Release Sprintctl 0.3.1 - #42
Merged
Merged
Conversation
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
1 participant
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.
Outcome\n\nPrepare the patch release that makes the merged revision-gated item-context pilot from PR #41 consumable as an immutable Sprintctl artifact.\n\n## Scope\n\n- bump project/runtime/lock metadata to 0.3.1\n- advance the exact release-contract validator to v0.3.1\n- no schema, behavior, deployment, or served-authority mutation\n\n## Verification\n\n- 1272 passed, 161 skipped with ambient session identifiers removed (CI-equivalent isolation)\n- exact wheel built: sprintctl-0.3.1-py3-none-any.whl\n- release validator passed for tag v0.3.1\n- git diff check passed\n\nThe first local suite run inherited CODEX_THREAD_ID and correctly exposed three ambient-reservation attribution differences; the isolated rerun removed all ambient session identifiers and passed.\n\nAfter independent review and merge, tag v0.3.1 will trigger the repository's gated, attested GitHub-only release workflow. Appservice/Vuoro pinning and rollout remain operator-owned and are not part of this PR.