Repository navigation
ci: update actions to Node 24 releases pinned by SHA - #15
Merged
Merged
Conversation
The old tags target Node 20, which GitHub now forces onto Node 24 with a deprecation warning.
🟢 Tier S · Ready to merge
Updated the GitHub Actions workflows to use Node 24-compatible action releases pinned to commit SHAs, with release versions noted in comments. The release publishing workflow and the checkout steps used by lint, static analysis, and E2E workflows are covered.
📂 Walkthrough · 4
Reviewed |
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
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.
The release build warns that its actions target Node 20, which is deprecated. This moves every action in the repo to its latest release and pins it by SHA, with the version in a comment.
build-and-push.ymlonly runs on a published release, so this PR does not exercise it. It takes effect on the next release.