Bump next/react/react-dom + @types/node (with lockfile)#11
Merged
Conversation
Dependabot PRs only touched package.json, so CI failed on `bun install --frozen-lockfile`. This consolidates the safe bumps: - next 16.2.6 → 16.2.11 (security advisories in 16.2.11) - react + react-dom 19.2.6 → 19.2.8 - @types/node 22.x → 26.1.1 TypeScript stays on 5.9.3: Next 16 cannot detect typescript@7 as installed (different package layout), so the TS 7 Dependabot PR is not safe yet.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Consolidates the open Dependabot dependency bumps with a real
bun.lockupdate so CI'sbun install --frozen-lockfilesucceeds.nextreactreact-dom@types/nodetypescriptWhy not merge the Dependabot PRs as-is
Every open Dependabot PR failed CI with:
Dependabot updated
package.jsonwithout regeneratingbun.lock.Why not TypeScript 7 (#7)
next builddoes not recognizetypescript@7.0.2as installed (native optional package layout) and falls into a broken yarn auto-install path that crashes withThe "id" argument must be of type string. Keep 5.9.3 until Next supports TS 7.Test plan
bun install --frozen-lockfilebun run typecheckbun run build