ci: accept post-release tags (0.4.0-1) for Python-only re-releases - #4
Merged
Merged
Conversation
The release tag doubled as the browser release to download and the wheel version, so fixing the wheels or the client required a new browser release. The params job now splits the tag: 0.4.0-1 (or 0.4.0.post1) bundles browser 0.4.0 and publishes the PEP 440 post-release 0.4.0.post1. Malformed tags fail in the params job, and workflow_dispatch gains a matching post input.
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.
Summary
lightpanda-io/browserrelease to download and as the wheel version, so re-publishing fixed wheels or client fixes needed a new browser release.paramsjob now splits the tag:0.4.0-1(Debian style) or0.4.0.post1bundles browser0.4.0and publishes the PEP 440 post-release0.4.0.post1. PlainX.Y.Ztags behave as before. Malformed tags fail inparamsinstead of on a matrix leg.workflow_dispatchgains an optionalpostinput for TestPyPI dry runs.==0.4.0pin does not pick up post-releases (use~=0.4.0).Rollout
paramsjob on thenightlypath.workflow_dispatchwith release0.4.0, post1, publishtestpypi.0.4.0-1and approve thepypideployment.