Conversation
…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
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughBoth Next.js templates update ChangesNext.js template dependency updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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
template-nextjs-esm/package.jsonESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox. template-nextjs/package.jsonESLint 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. Comment |
Summary
nextandeslint-config-nextfrom 16.2.10 to 16.2.12 intemplate-nextjsandtemplate-nextjs-esm, clearing all 18 open Dependabot security alerts (7 high, 11 moderate) — all traced tonext@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).package-lock.jsonto 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-eslint/parser@8.65.0's peer dependency caps attypescript >=4.8.4 <6.1.0, so installing typescript 7 breaksnpm installwith 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 lintnpm run typechecknpm run buildRelated to PP-3913.
Merge Request:
origin/develop→origin/mainSummary by CodeRabbit