Repository navigation
ci: upgrade actions and isolate the publish job - #6
Merged
Merged
Conversation
Use the current action majors (checkout v7, setup-node v7, release-please v5, create-pull-request v8, upload-artifact v7), which run on Node 24 and support `package-manager-cache`. Split the npm publish into its own job so a failed publish can be re-run without re-running release-please.
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
2 participants
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.
What
actions/checkout@v7,actions/setup-node@v7,googleapis/release-please-action@v5,peter-evans/create-pull-request@v8,actions/upload-artifact@v7. All run on Node 24 and supportpackage-manager-cache.release-please.yml(needs: release), so a failed publish can be retried with "Re-run failed jobs" without re-running release-please.Why
The first automated publish of
1.3.1failed with E404 because the npm trusted publisher is not configured yet, and the previous workflow could not retry the publish on its own.Test plan
release-please.yml(andpublish.ymlfor manual runs)1.3.1via the manual Publish workflow, or let the next release publish automatically