Skip to content

fix(bifrost): pin Node engines so Vercel stops building on Node 20 - #5843

Merged
chitalian merged 1 commit into
mainfrom
fix-bifrost-build
Oct 19, 2026
Merged

chitalian merged 1 commit into
mainfrom
fix-bifrost-build

Conversation

@chitalian

Copy link
Copy Markdown
Contributor

Problem

Every new helicone-bifrost deployment on Vercel has failed since the project's first build after October 1, 2026. That includes the production deploy for #5841 and the preview for #5842. Each one failed 5 to 11 seconds after it started, which is before yarn install or next build could have run. The helicone and helicone-eu projects deployed the same commits without problems.

Root cause

Vercel disabled Node.js 20 for new deployments on October 1, 2026. bifrost/package.json has no engines field, so the bifrost project falls back to the Node version in its Project Settings, which still points at 20. web/package.json declares "engines": { "node": ">=20" }, so the web projects get the newest supported Node and keep deploying.

The timeline fits:

  • The last successful bifrost build was on Aug 31, before the cutoff.
  • Every public commit between then and Sync security fixes from private repo #5841 skipped bifrost ("Not affected").
  • The first two builds after the cutoff both failed within seconds.
  • No bifrost config changed in that window: vercel.json, next.config.mjs and package.json are untouched. The only lockfile change removes an unused @codesandbox/sdk entry.

I can't read the Vercel logs, so the exact Vercel error message is unconfirmed. The diagnosis rests on the evidence above.

Fix

Add the same "engines": { "node": ">=20" } to bifrost/package.json that web/ and the repo root already use. Vercel uses engines in place of the Project Settings version, and for a >= range it picks the newest supported major.

I didn't pin an exact major such as 24.x because yarn 1 enforces workspace engines on every root yarn install. A pin would break the CI jobs and Docker images that still install on Node 20. With >=20, those installs keep passing.

Verification

All on this branch, after a clean yarn install --frozen-lockfile:

  • Node 24.22.0: yarn build (next build plus the next-sitemap postbuild) passed. ✓ Compiled successfully, ✓ Generating static pages (4669/4669), sitemap written, Done.
  • Node 22.22.1: the same build passed.
  • yarn 1 enforces workspace engines: with a non-matching value, root installs fail with The engine "node" is incompatible with this module. With >=20 they pass.

One caveat: during testing my IP got blocked by GitHub's unauthenticated API (api.github.com/repos/helicone/helicone returned a 403 HTML page). The build fetches that URL for the star count in app/components/Layout.tsx and components/home/OpenSource.tsx, so the 403 made prerendering fail. For the final runs I replaced that one fetch with a fixed star count through a local --require hook, which is not part of this change. That fetch has no error handling, so a GitHub rate limit on Vercel would fail the build in the same way. That deserves its own follow-up.

Changing the Node version in the helicone-bifrost Project Settings to 22.x or 24.x would also fix this. This PR does it in the repo, so the setting can't drift again.

🤖 Generated with Claude Code

Vercel disabled Node.js 20 for new deployments on October 1, 2026.
bifrost/package.json had no engines field, so the helicone-bifrost
project fell back to its Project Settings Node version and every new
deployment failed within seconds, before install or next build ran.

Add the same "engines": { "node": ">=20" } that web/ and the repo root
already declare. Vercel lets engines override Project Settings and picks
the newest supported major for a >= range, which is how the web projects
deploy the same commits successfully. The range keeps yarn's workspace
engines check passing for CI and Docker images that still use Node 20.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Oct 19, 2026

Copy link
Copy Markdown

Bugbot is paused — your team has an unpaid invoice

Bugbot is paused because your team has an unpaid invoice.

Pay it from the billing page in the Cursor dashboard and Bugbot resumes automatically.

(requestId: 80b7e240-0769-4540-8158-8642a9925de5)

@vercel

vercel Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
helicone-bifrost Ready Ready Preview Oct 19, 2026 6:45pm UTC
2 Skipped Deployments
Project Deployment Actions Updated
helicone Skipped Skipped Oct 19, 2026 6:45pm UTC
helicone-eu Skipped Skipped Oct 19, 2026 6:45pm UTC

Request Review

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Your trial has ended. Reactivate Greptile to resume code reviews.

@supabase

supabase Bot commented Oct 19, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project bolqqmqbrciybnypvklh because there are no changes detected in supbase/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@supabase

supabase Bot commented Oct 19, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project lmahfbbnchpworytrrqk because there are no changes detected in .supabase/supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@claude

claude Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Claude encountered an error —— View job


I'll analyze this and get back to you.

@chitalian
chitalian merged commit fe76e70 into main Oct 19, 2026
8 of 9 checks passed
@chitalian
chitalian deleted the fix-bifrost-build branch October 19, 2026 19:06

This branch was successfully deployed

1 active and 2 inactive deployments
Preview – helicone-bifrost — 37adc461 Deployed Oct 19, 2026 by vercel[bot]
Preview – helicone — 37adc461 Deployed Oct 19, 2026 by vercel[bot]
Preview – helicone-eu — 37adc461 Deployed Oct 19, 2026 by vercel[bot]
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