chore: Bump actions off Node.js 20#105
Open
dervoeti wants to merge 1 commit into
Open
Conversation
6 tasks
dervoeti
force-pushed
the
chore/bump-node20-actions
branch
from
e1d7b92 to
352567d
Compare
dervoeti
force-pushed
the
chore/bump-node20-actions
branch
from
352567d to
5767ec8
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
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.
We'll soon be affected by this (see the warnings in this PR run for example):
This PR bumps three actions to get off Node.js 20 before the GitHub Actions runner deprecation:
docker/login-actionv3.6.0 -> v4.1.0docker/setup-buildx-actionv3.12.0 -> v4.0.0anchore/sbom-action/download-syftv0.21.1 -> v0.24.0Swatinem/rust-cachev2.8.2 -> v2.9.1slackapi/slack-github-actionv2.1.1 -> v3.0.3replicatedhq/replicated-actions/{create,remove}-clusterv1.19.0 -> v1.26.0All three releases switch the runtime to Node.js 24.
I checked the changelogs for breaking changes (also Syft changelog), didn't spot anything that would affect us.