Skip to content

chore(deps): bump next.js version#1112

Merged
james-elicx merged 2 commits intomainfrom
james/bump-next-deps
May 6, 2026
Merged

chore(deps): bump next.js version#1112
james-elicx merged 2 commits intomainfrom
james/bump-next-deps

Conversation

@james-elicx
Copy link
Copy Markdown
Collaborator

No description provided.

@james-elicx
Copy link
Copy Markdown
Collaborator Author

/bigbonk review

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 6, 2026

Open in StackBlitz

npm i https://pkg.pr.new/vinext@1112

commit: eba5b63

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 6, 2026

Example Preview Production Original
app-router-cloudflare preview production
pages-router-cloudflare preview production
app-router-playground preview production original
realworld-api-rest preview production
nextra-docs-template preview production
benchmarks preview production
hackernews preview production original

Copy link
Copy Markdown
Contributor

@ask-bonk ask-bonk Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Straightforward dependency bump. Reviewed all four files:

  1. pnpm-workspace.yaml — Catalog bumped next from 16.2.3 to 16.2.5. Also adds next to minimumReleaseAgeExclude, which makes sense since Next.js is a core dependency that should be updatable without the 24h release age gate.

  2. benchmarks/nextjs/package.json — Pinned versions bumped for the Next.js baseline benchmark (next 16.2.3→16.2.5, react/react-dom 19.2.4→19.2.6). This package is correctly outside the pnpm workspace since it's the vanilla Next.js comparison target.

  3. .github/workflows/ci.ymlcreate-next-app version bumped from 16.2.3 to 16.2.5 to match.

  4. pnpm-lock.yaml — Lockfile correctly reflects the version changes across all workspace consumers. Also cleans up stale baseline-browser-mapping@2.10.0 and caniuse-lite@1.0.30001776 entries that are no longer needed (Next.js 16.2.5 depends on the newer versions already present in the lockfile).

LGTM — CI still running but Check has already passed.

@ask-bonk
Copy link
Copy Markdown
Contributor

ask-bonk Bot commented May 6, 2026

Reviewed and approved PR #1112. Summary of what the PR does:

  • Bumps next from 16.2.3 to 16.2.5 across the catalog, benchmarks, and CI workflow
  • Bumps react/react-dom from 19.2.4 to 19.2.6 in the Next.js benchmark baseline
  • Adds next to minimumReleaseAgeExclude so it can be updated without the 24h release age gate
  • Lockfile cleanup removes stale baseline-browser-mapping@2.10.0 and caniuse-lite@1.0.30001776 that were only needed by the old Next.js version

Everything is consistent and CI Check has passed. The remaining CI jobs (Vitest, E2E, deploys) are still running.

github run

@james-elicx james-elicx force-pushed the james/bump-next-deps branch from eed363a to cf6dcbd Compare May 6, 2026 17:24
@james-elicx james-elicx enabled auto-merge (squash) May 6, 2026 17:27
@james-elicx james-elicx merged commit b631b5d into main May 6, 2026
33 checks passed
@james-elicx james-elicx deleted the james/bump-next-deps branch May 6, 2026 17:32
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