ci(release): create GitHub releases on tag push, drop release-drafter - #42
Open
ykdojo wants to merge 1 commit into
Open
ci(release): create GitHub releases on tag push, drop release-drafter#42ykdojo wants to merge 1 commit into
ykdojo wants to merge 1 commit 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
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.
Removes release-drafter and makes tag pushes produce GitHub releases with auto-generated notes, so the Releases page matches the tag-driven publish flow this repo actually uses.
Why
publish-package.yml), never via GitHub releases. Release-drafter assumes the opposite flow: it keys the next version off the last published GitHub release, and since none existed it sat stuck at av0.0.1draft reading "No changes" (that stale draft is already deleted; without this change the next merge to main recreates it).Contents
.github/workflows/release-drafter.yml+ its.github/release-drafter.ymlconfig.publish-package.yml: after the PyPI upload on a tag push, rungh release create "$GITHUB_REF_NAME" --generate-notes --verify-tag(job gainscontents: write). Guarded topushevents only, soworkflow_dispatch/TestPyPI runs never create releases.AGENTS.md: correct the Versioning & Publishing section - the trigger is av*tag push, not publishing a GitHub release - and add the two-command release recipe.