Repository navigation
Bump checkout and setup-node to v7 in publish workflow - #330
Merged
Merged
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.
Follow-up to #314, aligning
npmpublish.ymlwith #329 (which updates the other workflows).actions/checkoutv4 -> v7 andactions/setup-nodev4 -> v7. Provenance andpermissionsfrom Update publish workflow actions and enable npm provenance #314 are unchanged.registry-urlbehaves the same in setup-node v7. The one v7 breaking change is that the dummyNODE_AUTH_TOKENfallback was removed, sonpm cinow runs with the token unset. Per the setup-node README this only affects Yarn Classic or older npm; this workflow uses npm on Node 24 (npm 11).NODE_AUTH_TOKENis still set on thenpm publishstep.packageManagerfield in package.json, so v5+ automatic caching stays off. Nopull_request_target/workflow_runtriggers, so the checkout v7 fork-checkout restriction does not apply.