Repository navigation
ci: qualify commit-bound Specs releases - #18
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
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
Replace the tag-triggered Specs release with an explicit version and full main-commit candidate. Build the wheel, sdist, manifest, and revision-identified docs once, reuse those exact artifacts through publication, and verify PyPI, GitHub release assets, installation, and deployed documentation after publication. Ordinary docs CI now builds and checks content without deploying unreleased versions.
The workflow also pins the current ecosystem qualification policy, including the accepted Python 3.15 exception ranges used across stable libraries.
Compatibility
Verification
typassesRelease
Merge before dispatching the Specs 0.1.5 metadata release.