fix: --write-baseline refuses a dev-source stack#5
Merged
Conversation
…stack Nightly releases are wheels/tags-only: source main never gets a version-bump commit, so a source-checkout/PYTHONPATH/editable stack reports the last-committed version string (currently 2026.7.6.649) while PyPI moves on. A baseline snapshotted from one silently pins a version the release train has passed — the exact incident the wiki-currency CI caught on PR #3. write_baseline() now inspects the install kind and refuses dev stacks with a message naming the clean-venv procedure (env -u PYTHONPATH matters: an ambient PYTHONPATH aliases even a fresh venv back to local source); --allow-dev-stack overrides deliberately. Regression test added; the skill documents the guard. Verified live: dev stack refused, release-wheel venv writes a byte-identical baseline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the recurrence path of the PR #3 CI catch: nightly releases are wheels/tags-only, so dev-source stacks permanently report the last-committed version (
2026.7.6.649today) while PyPI moves on.--write-baselinenow refuses such a stack (override:--allow-dev-stack), with the clean-venv procedure in the error message and the skill doc. Regression test added (suite 53/53); verified live in both directions — the release-wheel venv writes a byte-identical baseline.The permanent automation half is the already-filed PyAutoBuild wiring prompt (baseline regenerated from the release wheel at each release, as autolens_assistant gets today).
🤖 Generated with Claude Code