Skip to content

chore: bump action runtime to node24 (v0 backport)#116

Open
ronens88 wants to merge 1 commit intorelease/v0from
chore/node24-bump-v0
Open

chore: bump action runtime to node24 (v0 backport)#116
ronens88 wants to merge 1 commit intorelease/v0from
chore/node24-bump-v0

Conversation

@ronens88
Copy link
Copy Markdown
Contributor

@ronens88 ronens88 commented May 8, 2026

Summary

  • Backport of chore: bump action runtime to node24 #115 to the v0 maintenance line, branched from the v0.10.0 tag.
  • Same two-line change: using: node20using: node24 in action.yml and attest/action.yml.
  • Without this, customers pinned to @v0 / @v0.10.0 break on September 16, 2026 when GitHub removes Node 20 support.

Why a v0 backport

  • Customers pinned to @v0 may be on v0 deliberately (haven't validated v1 hardening behavior, or v1 conflicts with their setup). Forcing them to v1 just to get a Node bump would couple the two changes unfairly.
  • Pure runtime bump — no behavior change, no v1 features pulled in.

Test plan

  • verify-pr workflow passes on this PR
  • After merge: tag v0.10.1 on release/v0, move floating v0 tag
  • Announce runner-version requirement to customers (self-hosted / GHES need a runner that ships Node 24)

ronens88 added a commit that referenced this pull request May 8, 2026
The v0 maintenance branch needs CI gating for backports like the
node24 bump (#116). Without this, PRs into release/v0 silently
skip the verify suite.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Backport of #115 to the v0 line. GitHub forces Node 24 on runners
June 2 and removes Node 20 support September 16, after which the
action would fail to start on Node-20-pinned runtimes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ronens88 ronens88 force-pushed the chore/node24-bump-v0 branch from f246913 to 419614f Compare May 8, 2026 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant