ci: bump actions to Node 24 runtime versions#512
Open
mbruzda-splunk wants to merge 1 commit into
Open
Conversation
Bumps all GitHub Actions still bundling the deprecated Node 20 runtime to their first major version that targets Node 24, resolving the "Node.js 20 is deprecated" warnings across all jobs. - actions/checkout v4 -> v5 - actions/setup-python v5 -> v6 - actions/download-artifact v4 -> v7 - actions/upload-artifact v4 -> v6 - actions/cache v4 -> v5 - amannn/action-semantic-pull-request v5.5.3 -> v6.1.1 - aws-actions/configure-aws-credentials v4 -> v6 - dorny/test-reporter v1.9.1 -> v3.0.0 - geekyeggo/delete-artifact v5 -> v6 - softprops/action-gh-release v2 -> v3 Actions already on Node 24 (setup-java@v5, create-github-app-token@v3, amazon-ecr-login@v2, upload-release-action@v2) and docker/composite actions (splunk/*, reuse-action, pre-commit, trufflehog, skywalking-eyes) are unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
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
Bumps all GitHub Actions still bundling the deprecated Node 20 runtime to their first major version that targets Node 24, resolving the
Node.js 20 is deprecatedwarnings across all jobs in this workflow family.actions/checkoutactions/setup-pythonactions/download-artifactactions/upload-artifactactions/cacheamannn/action-semantic-pull-requestaws-actions/configure-aws-credentialsdorny/test-reportergeekyeggo/delete-artifactsoftprops/action-gh-releaseApplied consistently across all four workflow files:
reusable-build-test-release.ymlbuild-test-release.yamlreusable-publish-to-splunkbase.ymlreusable-validate-deploy-docs.ymlLeft unchanged (already Node 24, or docker/composite)
setup-java@v5,create-github-app-token@v3,amazon-ecr-login@v2,svenstaro/upload-release-action@v2, and all docker/composite actions (splunk/*,fsfe/reuse-action,pre-commit/action,trufflehog,skywalking-eyes).Testing
Ran the full
build-test-releasepipeline onsplunk-add-on-for-microsoft-cloud-servicespointed at this branch — pipeline succeeded, and the Node 20 deprecation warnings are gone from every job that consumes these actions (build, setup, meta, unit tests, all appinspect jobs, etc.).https://github.com/splunk/splunk-add-on-for-microsoft-cloud-services/actions/runs/28662878022
Known remaining warnings (out of scope — external sources)
pre-commitjob →actions/cache@v4is hardcoded insidepre-commit/action@v3.0.1(latest release).semgrep / sast-scanjob →checkout@v4/upload-artifact@v4come fromsplunk/sast-scanning/.github/workflows/sast-scan.yml@main(separate repo; addressed here: ci: bump actions to Node 24 runtime versions sast-scanning#7).🤖 Generated with Claude Code