Repository navigation
ticket-227: sync release metadata with 0.1.127 - #271
Closed
tom-sapletta-com wants to merge 1 commit into
Closed
tom-sapletta-com wants to merge 1 commit into
tom-sapletta-com wants to merge 1 commit into
Conversation
…ion from pyproject (ticket-227)
Contributor
Author
|
Closing this stale PR as superseded. Its implementation is already present on current |
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.
ticket-220 bumped pyproject/uv.lock to 0.1.127 but not planfile/release-metadata.json, so test_release_availability fails on main and on every PR. PyPI serves 0.1.127 (requires_python >=3.10); metadata now matches, and the test reads the version from pyproject.toml instead of a literal. Full suite: 1280 passed, 6 skipped. See project/ticket-227/README.md.