Skip to content

chore(deps): bump next 16.2.12 and refresh lockfile to latest in-range versions - #225

Merged
sergak01 merged 2 commits into
mainfrom
develop
Aug 3, 2026
Merged

chore(deps): bump next 16.2.12 and refresh lockfile to latest in-range versions#225
sergak01 merged 2 commits into
mainfrom
develop

Conversation

@sergak01

@sergak01 sergak01 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump next and eslint-config-next from 16.2.10 to 16.2.12 in template-nextjs and template-nextjs-esm, clearing all 18 open Dependabot security alerts (7 high, 11 moderate) — all traced to next@16.2.10 (middleware/proxy bypass, SSRF in rewrites and Server Actions, DoS in Server Actions and the SVG image optimizer, cache confusion, unauthenticated Server Function endpoint disclosure).
  • Refreshed package-lock.json to the latest versions already permitted by existing devDependency ranges: eslint, prettier, semantic-release, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, and transitively js-yaml/form-data.

Not included

  • typescript 6.0.3 → 7.0.2 was attempted but reverted: @typescript-eslint/parser@8.65.0's peer dependency caps at typescript >=4.8.4 <6.1.0, so installing typescript 7 breaks npm install with an ERESOLVE conflict in every template that lints with @typescript-eslint. Needs to wait for typescript-eslint to add TS7 support.

Included commits

Testing

  • npm run lint
  • npm run typecheck
  • npm run build
  • Scaffolded vanilla, vanilla-ts, react, nextjs, and nextjs-esm via the built CLI against the real npm registry; verified install/build for each

Related to PP-3913.

Merge Request: origin/developorigin/main

Summary by CodeRabbit

  • Bug Fixes
    • Updated the Next.js framework and its linting configuration to version 16.2.12 in both starter templates.
    • Includes the latest maintenance fixes and improvements from these updates.

…e versions

Bump next and eslint-config-next from 16.2.10 to 16.2.12 in template-nextjs
and template-nextjs-esm. This clears all 18 open Dependabot security alerts
(7 high, 11 moderate), all of which trace to next@16.2.10: middleware/proxy
bypass, SSRF in rewrites and Server Actions, DoS in Server Actions and the
SVG image optimizer, cache confusion, and unauthenticated Server Function
endpoint disclosure. Supersedes dependabot PRs #217, #218, #219, #220.

Also ran `npm update` at the root to refresh package-lock.json to the latest
versions already allowed by existing devDependency ranges: eslint, prettier,
semantic-release, @typescript-eslint/eslint-plugin, @typescript-eslint/parser,
and transitively js-yaml and form-data. Supersedes dependabot PRs #175, #176,
#177, #178, #181, #191, #193.

Did not bump typescript 6.0.3 -> 7.0.2 (dependabot PRs #199, #200, #202,
#205): @typescript-eslint/parser@8.65.0's peer dependency caps at
"typescript >=4.8.4 <6.1.0", so installing typescript 7 breaks `npm install`
with an ERESOLVE conflict in every template that lints with
@typescript-eslint (verified by scaffolding vanilla-ts via the built CLI).
Left at 6.0.3 until typescript-eslint adds TS7 support.

Verified: lint, typecheck, and build pass at the root; scaffolded vanilla,
vanilla-ts, react, nextjs, and nextjs-esm via the built CLI against the real
registry to confirm install/build still work with the bumped versions.

Related to PP-3913.
chore(deps): bump next 16.2.12 and refresh lockfile to latest in-range versions
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7a53a151-78e0-4898-89e7-f7a2ba809426

📥 Commits

Reviewing files that changed from the base of the PR and between 9da78b4 and 4ac6afc.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • template-nextjs-esm/package.json
  • template-nextjs/package.json

📝 Walkthrough

Walkthrough

Both Next.js templates update next and eslint-config-next from 16.2.10 to 16.2.12.

Changes

Next.js template dependency updates

Layer / File(s) Summary
Update Next.js dependencies
template-nextjs/package.json, template-nextjs-esm/package.json
Both templates update next and eslint-config-next to version 16.2.12.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: michailozdemir, maksymovvolodymyr

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the dependency updates and lockfile refresh described in the pull request.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

template-nextjs-esm/package.json

ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.

template-nextjs/package.json

ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sergak01
sergak01 merged commit 3eabeb5 into main Aug 3, 2026
3 checks passed
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.

2 participants