Fix 0.1.29 release workflow - #295
Merged
Merged
Conversation
Contributor
|
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.
What changed
tomllibversion parsing with a shell extraction that works on the existing Python 3.10 release runner0.1.29release without another version bumpRoot cause
The first
Release packagerun failed before build/publish becausetomllibis unavailable in Python 3.10. No package was uploaded to PyPI and no GitHub release was created.Expected result
Merging this PR should trigger the corrected release workflow, publish
rtichoke==0.1.29through the existing OIDC trusted-publishing setup, and create GitHub releasev0.1.29.