ci: create GitHub Release on tag push (parity with armory-todo)#4
Merged
Conversation
Mirror armory-todo's release.yml: bump permissions contents: read → contents: write and add an idempotent 'Create GitHub Release' step that runs after publish (if: success(), so it still fires when npm publish was skipped as already-published). Uses the auto-provided github.token with gh CLI — no third-party action. Keeps GitHub Releases in sync with npm on every v* tag.
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.
Mirror armory-todo's release.yml so every
v*tag also creates a GitHub Release (auto-generated notes), in sync with the npm publish.Changes:
permissions: contents: read→contents: write(needed to create releases on tag push)if: success()— fires even when npm publish was skipped as already-published)github.token+ghCLI — no third-party actionCloses the release-CI parity gap with armory-todo. No behavior change to the publish job itself.