Skip to content

feat: bump runtime to node24#3

Open
Icantjuddle wants to merge 1 commit intomainfrom
devin/1778100900-bump-node24
Open

feat: bump runtime to node24#3
Icantjuddle wants to merge 1 commit intomainfrom
devin/1778100900-bump-node24

Conversation

@Icantjuddle
Copy link
Copy Markdown

@Icantjuddle Icantjuddle commented May 6, 2026

Summary

GitHub Actions deprecates the Node.js 20 runtime on June 2, 2026. This fork (Exafunction/github-cherry-pick-action) is currently pinned to runs.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-conflicts and "include conflicted file names in PR description" that aren't in upstream carloscastrojumo/github-cherry-pick-action, and upstream itself is still on node20).

Changes:

  • action.yml: runs.using: node20node24.
  • package.json: @types/node ^20.12.4^24.0.0.
  • package-lock.json: regenerated.

The bundled dist/index.js is byte-identical to the previous build (since no source files changed) — npm run package produces the same ncc output. Only the declared runtime changes.

Verified locally with npm run all (test + format-check + lint + build):

  • 3/3 jest tests pass.
  • prettier reports all files unchanged.
  • eslint passes.
  • tsc && ncc build succeeds.

After this merges, a follow-up PR in Exafunction/Exafunction will re-pin the consumer workflow to the new SHA.

Review & Testing Checklist for Human

  • Confirm the build workflow (.github/workflows/test.yaml) passes on this PR — that's the canonical end-to-end check (npm run all on ubuntu-latest).
  • Sanity-check that dist/index.js was not modified by the rebuild — the diff should show only action.yml, package.json, and package-lock.json. (If dist/index.js did 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

Status Commit
🟢 Reviewed ef8dbaa
Open in Devin Review (Staging)

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>
@staging-devin-ai-integration
Copy link
Copy Markdown

Original prompt from B

can you audit the exafunction/exafunction repo for any action external or internal that is using a node20 action which will be deprecated on June 2. For actions we have forked into the Exafunction org we should switch to their upstream where possible.

@staging-devin-ai-integration
Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Copy link
Copy Markdown

@staging-devin-ai-integration staging-devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review (Staging)
Debug

Playground

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