Bump harden-runner to v2.20.1 for Node 24 runtime - #98
Open
justaugustus wants to merge 1 commit into
Open
Conversation
step-security/harden-runner v2.15.0 declares `using: node20`, so GitHub now force-runs it on Node 24 and emits a deprecation warning on every job: Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: step-security/harden-runner@... v2.20.1 ships a Node 24 runtime, which clears the warning. Update the SHA-pinned reference in the Production sync and GitHub sync tests workflows. Assisted-by: Claude Code:claude-opus-4-8 Signed-off-by: Stephen Augustus <[email protected]>
|
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
Bump
step-security/harden-runnerfrom v2.15.0 → v2.20.1 (SHA-pinned) in theProduction syncandGitHub sync testsworkflows.Why
v2.15.0 declares
using: node20, so GitHub now force-runs it on Node 24 and emits a deprecation warning on every job:v2.20.1 ships a
node24runtime (verified in itsaction.yml), which clears the warning. Pin:b09bb98e06d4d774595224525879c09bc6e98c40= v2.20.1.Notes
egress-policy: auditis unchanged.lint.ymladded in Fix malformed org config and add pre-merge lint guard #97 still references v2.15.0; it should get the same bump once Fix malformed org config and add pre-merge lint guard #97 merges (or Dependabot will).