Skip to content

Pin next to ^16.2.6 to avoid broken 16.3.0-preview.0 release#476

Open
brianstrauch wants to merge 1 commit into
mainfrom
pin-next-version
Open

Pin next to ^16.2.6 to avoid broken 16.3.0-preview.0 release#476
brianstrauch wants to merge 1 commit into
mainfrom
pin-next-version

Conversation

@brianstrauch

Copy link
Copy Markdown
Member

What was changed

Pin next to ^16.2.6 in nextjs-ecommerce-oneclick (was latest) and update the lockfile.

Why

npm's latest dist-tag for next currently points to 16.3.0-preview.0, whose @next/swc-linux-x64-gnu binary was never published. Any CI job that resolves next@latest fresh (or any regenerated lockfile) picks up the broken preview and next build fails with a 404 downloading the SWC binary:

⨯ Failed to download swc package from https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-16.3.0-preview.0.tgz
unhandledRejection Error: request failed with status 404

Pinning to ^16.2.6 keeps the existing stable resolution and excludes prereleases.

🤖 Generated with Claude Code

@brianstrauch brianstrauch requested a review from a team as a code owner June 9, 2026 21:32
@brianstrauch brianstrauch enabled auto-merge (squash) June 9, 2026 21:37
npm's 'latest' dist-tag for next currently points to 16.3.0-preview.0,
whose @next/swc-linux-x64-gnu binary is not published, so 'next build'
fails with a 404 whenever the lockfile is regenerated.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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