ci: enable GitHub releases and adjust permissions in publish workflow #257
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
…workflow **Added:** - Add step to create a GitHub release with autogenerated notes if release does not exist, using the `gh` CLI in the publish workflow **Changed:** - Update workflow permissions from `contents: read` to `contents: write` to allow release creation
…tion-in-publish-workflow
l50
deleted the
jayson/eng-3692-automate-github-release-creation-in-publish-workflow
branch
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.
Key Changes:
Added:
check for an existing release and create one with generated notes if absent
GH_TOKENfor authentication withGitHub CLI during release creation
Changed:
contentspermission fromreadtowritetosupport GitHub release creation in the workflow
Generated Summary:
readtowrite.This summary was generated with ❤️ by rigging