fix(ci): release permissions and Node.js 24#118
Merged
Conversation
Allow GITHUB_TOKEN to create GitHub releases on merged PRs, update workflow runners to Node.js 24, and add workflow_dispatch to retry failed releases. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
contents: writeto the release workflow soGITHUB_TOKENcan create GitHub releasesGITHUB_TOKENexplicitly tosoftprops/action-gh-releaseworkflow_dispatchto retry a failed release manuallyWhy
The v3.0.0 release failed with
Resource not accessible by integrationbecause PR-triggered workflows default to read-only token permissions.After merge
mainto publish v3.0.0Releaselabel as beforeTest plan
v3.0.0is created and Marketplace publish succeedsMade with Cursor