Repository navigation
Run the Vercel CLI under Node in the deploy job - #8
Merged
Merged
Conversation
Under Bun, with no node_modules when the CLI started, the Next.js builder resolved next through Bun's auto-install cache (16.4.1) instead of the locked 16.4.0, and the build output referenced files in that cache, which Vercel could not read. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 14, 2026
This branch was successfully deployed
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
1 participant
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.
Fixes #10
The first automated release (0.2.0) verified and tagged, but its deploy failed (run 38641065333). Vercel stopped while downloading the prebuilt files:
Production still serves the earlier manual deployment.
Cause
deploy-production.shran the Vercel CLI under the Bun runtime (bunx --bun). When the CLI started, the checkout had nonode_modules, so Bun's auto-install was active. The CLI's Next.js builder then resolvednextthrough Bun's global cache: it installed the latest release (16.4.1) instead of using the locked 16.4.0 thatvercel buildinstalled moments later. The function configs in the build output then pointed at a file in~/.bun/install/cache, which doesn't exist on Vercel's side.Change
deploy-production.shruns the same pinned CLI,vercel@58.8.0, throughnpx, so it runs under Node.changelog.d/deploy-cli-under-node.fixed.md: merging releases 0.2.1 and deploys it.Evidence
Local builds of the 0.2.0 release commit (
1dfe03a2), each from a fresh checkout:A Node-built output of the same commit was deployed as a preview (not production) with
vercel deploy --prebuilt, and reachedREADY.Format check, actionlint and
bash -npass locally. The deploy job itself only runs onmain, so this PR's checks don't exercise it.No environment variable changes.
VERCEL_TOKEN(GitHubProductionenvironment),VERCEL_ORG_IDandVERCEL_PROJECT_ID(inline in the job) are wired as before.🤖 Generated with Claude Code