chore(ci): update actions to v5 and add pre-commit script to sync package-lock#53
Merged
Merged
Conversation
Both actions still declare node20 as their internal runtime, triggering Github's Node 20 deprecation warning on every run. v5 of each uses node24 internally; no input/output changes affect our usage.
conventional-changelog-action only bumps the top-level "version" field, leaving package-lock.json's nested packages[""] entry (its own copy of the root version) stale after every release. This script regenerates the lockfile via `npm install --package-lock-only` and is meant to be wired up as the action's pre-commit hook.
The publish workflow fails when generating npm provenance via GitHub Actions. This is a known issue with older Node versions, where the OIDC token request used for provenance attestation returns a 404. Upgrading to Node 24 resolves the issue.
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.
What does this PR do?
npm install --package-lock-onlyand is meant to be wired up as the action's pre-commit hook. Can be removed once package-lock.json version not updated correctly TriPSs/conventional-changelog-action#257 is fixed