Skip to content

Release v0.2.1: version bump - #102

Merged
hsliuustc0106 merged 1 commit into
mainfrom
release-0.2.1
Oct 4, 2026
Merged

hsliuustc0106 merged 1 commit into
mainfrom
release-0.2.1

Conversation

@hsliuustc0106

Copy link
Copy Markdown
Contributor

v0.2.0 was tagged mid-day 2026-10-03 but never published; main has since landed flaky-watch and its refire fix (#88/#91/#93/#96), quarantine robustness (#97), watch-update (#95/#98), the claim protocol (#92), and timestamped runner logs (#99). Following the v0.1.0 precedent (tagged, superseded, never published), this bumps to 0.2.1 so the published tag, the npm payload, and the content agree — v0.2.0's payload would ship a known flaky-refire bug.

Version triple-synced (package.json / pyproject / init.py) + package-lock. Validated on the bumped tree: 707 Python tests, 25/25 launcher tests, package smoke PASS (global install --ignore-scripts, npx, runner, payload allowlist, versions). After merge: tag v0.2.1, re-draft the release, npm publish when the token lands.

@hsliuustc0106
hsliuustc0106 merged commit a4a2ec5 into main Oct 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant