Bun: Upgrade to Node JS 24

[yeikel]

What are you trying to accomplish?

Upgrade NodeJS to 24 for Bun as Node 20 reached end of life on April 30, 2026.

Anything you want to highlight for special attention from reviewers?

This unblocks #14963 for the bun ecosystem

How will you know you've accomplished your goal?

The build passes and all the existing tests continue to work

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[v-HaripriyaC]

QQ: @yeikel , this does not unblock the PR: #14963, I am hoping there are more PRs to unblock this PR?

[yeikel]

QQ: @yeikel , this does not unblock the PR: #14963, I am hoping there are more PRs to unblock this PR?

It unblocks #14963 specifically for the Bun ecosystem because Nodejs 20 is no longer published on that version of Ubuntu. It does not unblock it in general if that's what you meant. For that, there is still other work that needs to be completed

As soon as #14963 is ready, I'll move it back to ready

Thanks for helping!

added a comment

[yeikel]

@v-HaripriyaC I see you dismissed your review. Could you please clarify if anything else is not clear? Thanks!

[v-HaripriyaC]

@yeikel please see my comment above

[yeikel]

@yeikel please see my comment above

Did you see my response: #14964 (comment)

It does not fully unblock #14963 for all ecosystems but it does unblock it for bun

The reason #14963 cannot proceed is that Node JS 20 is no longer maintained and there is no Ubuntu 26 build for it

[v-HaripriyaC]

Thanks for the clarification, @yeikel. I understand now that this PR unblocks #14963 specifically for the Bun ecosystem, not more broadly. The change itself looks straightforward and low risk. I’ll hold off on final approval until you move this PR back to Ready for review.

[yeikel]

Thanks for the clarification, @yeikel. I understand now that this PR unblocks #14963 specifically for the Bun ecosystem, not more broadly. The change itself looks straightforward and low risk. I’ll hold off on final approval until you move this PR back to Ready for review.

Thank you. This change (#14964) is already ready for review. It is #14963 what is pending

[v-HaripriyaC]

LGTM

CI is green, which is great. Can we also confirm Bun-specific compatibility with Node 24 — especially image build success and a few representative Bun update/integration scenarios — to rule out runtime regressions from the Node 20 → 24 bump?

[yeikel]

CI is green, which is great. Can we also confirm Bun-specific compatibility with Node 24 — especially image build success and a few representative Bun update/integration scenarios — to rule out runtime regressions from the Node 20 → 24 bump?

Bun itself a an standalone binary that does not depend on NodeJS. The reason Node is defined in this ecosystem is because of the native helpers.

The build is already running a lot of integration tests plus unit tests for the helpers. Can you clarify what else are you looking for?

Thanks

[v-HaripriyaC]

I am able to check the relevant jobs/tests, thanks for being patient.

[v-HaripriyaC]

Workflow/job files

.github/workflows/ci.yml — ci (bun, bun, bun), integration, Updater, Lint, Rakefile Tests
.github/workflows/images-branch.yml — push-updater-images (includes bun), approval
.github/workflows/ci-arm64.yml — arm64-build (bundler-only, not Bun-specific)
Bun spec files

bun/spec/dependabot/bun/file_fetcher_spec.rb
bun/spec/dependabot/bun/file_updater_spec.rb
bun/spec/dependabot/bun/update_checker_spec.rb
bun/spec/dependabot/bun/update_checker/subdependency_version_resolver_spec.rb

[v-HaripriyaC]

Approving now