Repository navigation
馃懛 ci: publish GitHub Release after PyPI - #374
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
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.
Tag publication currently uploads to PyPI without creating a GitHub Release. Three older tags also have no section in the tracked changelog.
Restore those historical entries and create a GitHub Release after PyPI succeeds, with notes from the tagged changelog, a PyPI link, and a comparison to the previous version. GitHub write access belongs only to the release job; the package upload keeps OIDC only. The release App token remains scoped to this repository for the protected commit and tag push.