Repository navigation
chore(starters): update next to 16.3.8 - #366
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: NVIDIA/elements/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Signed-off-by: Cursor Agent <cursoragent@cursor.com>
coryrylan
force-pushed
the
topic/dependencies/starters/next
branch
from
October 2, 2026 17:49
9e38799 to
692c5df
Compare
coryrylan
approved these changes
Oct 2, 2026
Collaborator
|
🎉 This issue has been resolved in version 2.12.0 🎉 |
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
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.
Dependency
nextdependenciesinprojects/starters/nextjs/package.json(nextjs-starter)chore(starters)because starter packages are private and unpublished. No other Next package is a direct dependency.Release review
output: 'export'. The patch does not change engines (node >=20.9.0), peer ranges, or the MIT license. Published 2026-09-30T16:07:21Z, which satisfiesminimumReleaseAge(1140 minutes).reactandreact-dom19.2.8 remain inside the unchanged Next peer range.@lit-labs/nextjs@0.2.4already peersnext13–15 while this starter is on Next 16. This patch does not change that existing mismatch, and Lit SSR stays disabled in the starter.Generated files
pnpm-lock.yamlmovesnext,@next/env, and the@next/swc-*optional packages to 16.3.8, and updates the@lit-labs/nextjssnapshot key that peersnext.Validation
CI=1 mise exec -- pnpm install --no-frozen-lockfile— passedmise exec -- pnpm run notice— failed (ERR_PNPM_NO_SCRIPT;noticeis a Wireit task without a script entry)mise exec -- node ./projects/internals/ci/notice/index.js— passed, notices unchangedmise exec -- pnpm run ciinprojects/starters/nextjs— passed (24 scripts, 31s). That starter has noDEVELOPMENT.md;ciis the Wireit build and lint task.mise exec -- node .agents/skills/agent-dependencies/scripts/verify-update.js --type=chore --scope=starters— passedCI=1 mise exec -- pnpm install --frozen-lockfile— passedmise exec -- pnpm run cifrom the repository root, with Git LFS files checked out andFONTCONFIG_FILErejecting/usr/share/fonts/truetype/macos/*— passed (138 scripts, 24 skipped, 117.6s)git diff --check— passed