Repository navigation
chore: pin all version locations to pyproject on every hook run - #10
Merged
Merged
Conversation
tests/unit/test_release_version_sync.py asserts that every hand-maintained copy of the release version (uv.lock, __init__, both fnos manifests, the fnos docker-compose image tag, README shields badges) agrees with pyproject.toml. It shipped broken at 1.0.2b7 because nothing imports those files, so testmon import-graph selection never ran their tests and no CI job compared the copies. Makefile test-affected now force-runs the file in a second, plain (non-testmon) pytest: testmon reports "changed files: 0" for data-only changes and deselects the module even when passed positionally, and --testmon-forceselect only narrows, never widens. Only a non-testmon invocation is reliably un-deselectable. Proven by probe: a drifted version goes 4 failed / 2 passed; --testmon-force-select does not exist in pytest-testmon 2.2.0. Also: publish SKILL fork note (manual tag + ancestry repair, +ra.1 marker) and a format-all artifact (MemorySettings). Gate: make all green (4633 passed, 25 skipped, 0 failed) in the commit that introduced these files.
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
2 participants
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.
Tooling half of the release-integrity work (security half is in
fix/unc-path-guard).Closes the gap that shipped 1.0.2b7 with five stale version copies: nothing
imports the version manifest files, so testmon import-graph selection never
ran their tests and no CI job compared the copies.
tests/unit/test_release_version_sync.py— asserts every hand-maintainedcopy (uv.lock,
__init__.py, both fnos manifests, fnos docker-composeimage tag, README shields badges) agrees with
pyproject.toml.Makefile test-affected— runs the file in a second, plain (non-testmon)pytest. Proven by probe: testmon reports "changed files: 0" for data-only
changes and deselects the module even when passed positionally;
--testmon-forceselectonly narrows, never widens;--testmon-force-selectdoes not exist in pytest-testmon 2.2.0. Only anon-testmon invocation is reliably un-deselectable.
.cursor/skills/publish/SKILL.md— FORK NOTE: release steps 5-6 (manualtag + push + re-merge main into develop + ancestry verify +
+ra.1marker) are manual on this fork because Release / Auto Tag / Sync
workflows are disabled.
Gate: make all green (4633 passed, 25 skipped, 0 failed).