build: bump GitHub Actions to clear deprecation warnings - #304
Open
claude[bot] wants to merge 1 commit into
Open
build: bump GitHub Actions to clear deprecation warnings#304claude[bot] wants to merge 1 commit into
claude[bot] wants to merge 1 commit into
Conversation
Bump the Node.js 20-based action pins on the 3-x-y branch to their latest releases, which run on Node.js 24, so the Release and Check Semantic Commit workflows stop emitting "Node.js 20 is deprecated" warnings. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LakSmsxUYjgzRWgDHe3hPm
dsanders11
approved these changes
Sep 2, 2026
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.
Requested via Slack thread
Before: The workflows on the
3-x-ybranch pin several actions to releases that still run on the Node.js 20 runtime. Every run ofRelease(via the reusabletest.yml) andCheck Semantic Commitemits a "Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24" warning, and the private-workflows deprecation audit flags both runs.After: All affected actions are pinned to their latest releases, which run natively on Node.js 24, so the workflows run cleanly with no deprecation annotations. The pins match what
mainalready uses.How: Bumped the commit-SHA pins (keeping the existing
# vX.Y.Zcomment convention) for the actions named in the audit annotations, plus the two remaining Node.js 20 pins in the same workflow files that hit the identical deprecation:actions/checkoutv4.2.2 (test.yml,update-abi.yml) and v5.0.0 (release.yml) -> v7.0.1 (3d3c42e5aac5ba805825da76410c181273ba90b1). v4 targets Node.js 20 and is flagged in theReleaserun; v5 was bumped alongside so every workflow uses the same version.actions/setup-nodev4.3.0 (test.yml,update-abi.yml,check-electron-abi.yml) and v5.0.0 (release.yml) -> v7.0.0 (820762786026740c76f36085b0efc47a31fe5020). v4 targets Node.js 20 and is flagged in theReleaserun.amannn/action-semantic-pull-requestv5.5.3 -> v6.1.1 (48f256284bd46cdaab1048c3721360e808335d50) insemantic.yml. v5 targets Node.js 20 and is flagged in theCheck Semantic Commitrun.actions/github-scriptv7.0.1 -> v9.0.0 (3a2844b7e9c422d3c10d287c895573f7108da1b3) incheck-electron-abi.yml. Not named by the audit, but v7 also targets Node.js 20.actions/cachev4.2.3 -> v6.1.0 (55cc8345863c7cc4c66a329aec7e433d2d1c52a9) inupdate-abi.yml. Not named by the audit, but v4 also targets Node.js 20.Source: private-workflows "Audit Deprecations" run https://github.com/electron/private-workflows/actions/runs/33677359849 (artifact
audit-results.md), which lists node-abi runs 33202324022 (Release) and 33202115738 (Check Semantic Commit). Themainbranch already carries these versions, so this targets3-x-y.🤖 Generated with Claude Code
https://claude.ai/code/session_01LakSmsxUYjgzRWgDHe3hPm
Generated by Claude Code