Repository navigation
Publish new ParticleGAN versions on master merges - #561
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.
An unpublished ParticleGAN version will go through the existing release tests and publish to PyPI after the release PR merges into
master. The workflow checks the exact committed version on PyPI before building. The existing GitHub release fallback still validates the tag and allows retries of incomplete uploads.The publisher keeps
release.ymland thepypienvironment. Rollout addsmasteras an allowed ref alongside the existingv*tags. This changes release automation only and does not merge the opendeveloprelease PR.Verified the workflow gate against live PyPI 0.10.1, the matching
v0.10.1release path and a rejected mismatched tag.