feat: bump runtime to node24#3
Open
Icantjuddle wants to merge 1 commit intomainfrom
Open
Conversation
GitHub Actions deprecates the Node.js 20 runtime on June 2, 2026: https://github.blog/changelog/2025-09-25-actions-deprecating-the-node20-runtime-bundled-with-the-actions-runner/ This commit: - Bumps action.yml runtime from node20 -> node24. - Bumps @types/node devDependency from ^20.12.4 -> ^24.0.0. - Regenerates package-lock.json. The bundled dist/index.js is byte-identical to the previous build; only the runtime declared in action.yml changes. Tests: `npm run all` passes (test + format + lint + build). Co-Authored-By: Staging-Devin AI <166158716+staging-devin-ai-integration[bot]@users.noreply.github.com>
Original prompt from B
|
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
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.
Summary
GitHub Actions deprecates the Node.js 20 runtime on June 2, 2026. This fork (
Exafunction/github-cherry-pick-action) is currently pinned toruns.using: node20, so any consumer that pins to it past that date will start logging deprecation warnings, and eventually fail entirely once the runtime is removed from the runner image.We need to keep this fork (we have Cognition-only features such as
commit-conflictsand "include conflicted file names in PR description" that aren't in upstreamcarloscastrojumo/github-cherry-pick-action, and upstream itself is still onnode20).Changes:
action.yml:runs.using: node20→node24.package.json:@types/node^20.12.4→^24.0.0.package-lock.json: regenerated.The bundled
dist/index.jsis byte-identical to the previous build (since no source files changed) —npm run packageproduces the same ncc output. Only the declared runtime changes.Verified locally with
npm run all(test + format-check + lint + build):tsc && ncc buildsucceeds.After this merges, a follow-up PR in
Exafunction/Exafunctionwill re-pin the consumer workflow to the new SHA.Review & Testing Checklist for Human
buildworkflow (.github/workflows/test.yaml) passes on this PR — that's the canonical end-to-end check (npm run allonubuntu-latest).dist/index.jswas not modified by the rebuild — the diff should show onlyaction.yml,package.json, andpackage-lock.json. (Ifdist/index.jsdid change, that would indicate a transitive dep version bump in@actions/*rather than just the runtime change.)Notes
The corresponding consumer workflow that uses this action is
Exafunction/Exafunction/.github/workflows/release_jetbrains.yaml(and a couple of other Exafunction workflows). The consumer pin will be updated in a separate PR once this merges.Link to Devin session: https://staging.itsdev.in/sessions/9936486f6cb541818952715deb01d558
Requested by: @Icantjuddle
Devin Review
ef8dbaa