Repository navigation
RFE: is it possible to start making github releases?馃 - #785
Closed
victorwon2001 wants to merge 2 commits into
Closed
victorwon2001 wants to merge 2 commits into
victorwon2001 wants to merge 2 commits into
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
2 participants
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
Publish a GitHub Release for each official version tag after the existing PyPI deployment succeeds. The new, tag-restricted job has its own
contents: writepermission, skips releases that already exist, and uses--verify-tagwhen creating a release so it cannot create a new tag.Testing
Workflow lint, pre-commit, and all 219 pytest tests passed; local command simulations covered existing releases, new releases, and creation failures. Live GitHub publication and subscriber notifications can only be confirmed after a future official tag deployment.
Fixes #437