Repository navigation
fix(bifrost): pin Node engines so Vercel stops building on Node 20 - #5843
Conversation
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>
Bugbot is paused — your team has an unpaid invoiceBugbot 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) |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
Problem
Every new
helicone-bifrostdeployment 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 beforeyarn installornext buildcould have run. Theheliconeandhelicone-euprojects deployed the same commits without problems.Root cause
Vercel disabled Node.js 20 for new deployments on October 1, 2026.
bifrost/package.jsonhas noenginesfield, so the bifrost project falls back to the Node version in its Project Settings, which still points at 20.web/package.jsondeclares"engines": { "node": ">=20" }, so the web projects get the newest supported Node and keep deploying.The timeline fits:
vercel.json,next.config.mjsandpackage.jsonare untouched. The only lockfile change removes an unused@codesandbox/sdkentry.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" }tobifrost/package.jsonthatweb/and the repo root already use. Vercel usesenginesin 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.xbecause yarn 1 enforces workspaceengineson every rootyarn 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:yarn build(next buildplus thenext-sitemappostbuild) passed.✓ Compiled successfully,✓ Generating static pages (4669/4669), sitemap written,Done.The engine "node" is incompatible with this module. With>=20they pass.One caveat: during testing my IP got blocked by GitHub's unauthenticated API (
api.github.com/repos/helicone/heliconereturned a 403 HTML page). The build fetches that URL for the star count inapp/components/Layout.tsxandcomponents/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--requirehook, 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-bifrostProject 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