ci: update GitHub Actions for Node.js 24 - #5
Merged
raphink merged 1 commit intoAug 14, 2026
Merged
Conversation
Contributor
Author
|
The failure is expected as PR created from the fork |
bogdankrasko
marked this pull request as ready for review
August 5, 2026 13:54
- Update external GitHub Action references to the Node.js 24-compatible, digest-pinned revisions shown in the diff. Signed-off-by: Bohdan Krasko <bkrasko@cisco.com>
bogdankrasko
force-pushed
the
pr/bkrasko/update-workflows-to-nodejs24
branch
from
August 11, 2026 18:50
bb5ee31 to
c3eb23e
Compare
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 changed
actions/checkouttov7.0.1.actions/setup-gotov7.0.0.marocchino/sticky-pull-request-commenttov3.0.5.Files changed
.github/workflows/coverage.yml.github/workflows/go.ymlWhy
This work addresses isovalent/roadmap#3310.
GitHub Actions runners are moving to Node.js 24 and dropping older JavaScript runtimes. Updating these actions keeps the affected workflows operational after that transition.
External actions remain pinned to immutable commit SHAs so a mutable tag cannot change the workflow implementation without review.