fix: upgrade Next.js to 16.2.10 + migrate ESLint to v9 flat config#89
Draft
caimanoliveira wants to merge 2 commits into
Draft
fix: upgrade Next.js to 16.2.10 + migrate ESLint to v9 flat config#89caimanoliveira wants to merge 2 commits into
caimanoliveira wants to merge 2 commits into
Conversation
- Upgrade next from 16.2.0 to 16.2.10 to patch 14 high/moderate CVEs (DoS via Server Components, middleware bypass, cache poisoning, SSRF) - Fix broken `npm run lint`: next lint was removed in Next.js 16; replace with eslint CLI + eslint-config-next/core-web-vitals flat config - Add eslint + eslint-config-next as devDependencies - Fix react-hooks/purity lint error in PlanoAcaoWidget: move Date.now() call into useState lazy initializer (runs only on mount) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gq6FZKsniPF1FVXVzt6Yu3
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Python 3.9 is no longer available on GitHub Actions runners (only 3.10+). Upgrade to 3.12 and setup-python@v5 (v1 targets deprecated Node 20). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gq6FZKsniPF1FVXVzt6Yu3
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
2 participants
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
nextfrom16.2.0→16.2.10, patching 14 CVEs (high/moderate) including DoS via Server Components, middleware/proxy bypass, cache poisoning, SSRF via WebSocket upgrades, and XSS with CSP nonces.next lintwas removed in Next.js 16. Replaced"lint": "next lint"with"lint": "eslint ."and addedeslint+eslint-config-nextas devDependencies; createdeslint.config.mjsusing the new v9 flat config format (eslint-config-next/core-web-vitals).PlanoAcaoWidget.tsx): MovedDate.now()call from top-level render into auseStatelazy initializer, eliminating thereact-hooks/puritylint error.mentoria-crm/is excluded from root ESLint since it has its own config.What changed
package.jsonnext16.2.0 → 16.2.10; lint script; add eslint devDepspackage-lock.jsoneslint.config.mjsnext lint)src/components/trilhas/widgets/PlanoAcaoWidget.tsxDate.now()called during render → moved touseStatelazy initializerRemaining notes
Two moderate
postcssadvisories remain — their only available fix would downgrade Next.js to 9.3.3 (a breaking regression). These are bundled inside Next.js itself and require an upstream release to resolve.Generated by Claude Code