Skip to content

chore(security): bump next to 16.3.3 and eslint to ^10 - #15

Merged
cb-alish merged 1 commit into
mainfrom
bump/next-eslint-security
Sep 10, 2026
Merged

cb-alish merged 1 commit into
mainfrom
bump/next-eslint-security

Conversation

@cb-alish

@cb-alish cb-alish commented Sep 10, 2026 •

Copy link
Copy Markdown
Contributor

Security dependency bumps

Requested by the security team.

Changes

Package Before After
next 16.2.6 (lockfile was already 16.3.3) 16.3.3 pinned
eslint ^9 (9.39.5) ^10 (10.9.1)

ESLint 10 compatibility note

eslint-plugin-react@7.37.5 (a transitive dep via eslint-config-next) calls context.getFilename() which was removed in ESLint 10. This causes a crash at lint time.

Workaround applied in eslint.config.mjs: pin settings.react.version = "19.2.4" explicitly. This skips eslint-plugin-react's auto-detection code path that hits the removed API. Linting passes cleanly.

Upstream tracking: jsx-eslint/eslint-plugin-react#3977 / vercel/next.js#89764

Once eslint-plugin-react ships ESLint 10 support, the settings override can be removed.

Made with Cursor

Summary by CodeRabbit

  • Chores
    • Updated the app’s Next.js framework and ESLint tooling versions.
    • Improved React version handling in linting configuration for more consistent code analysis.

⚠️ Note: Your high-level summary instructions were not applied because this feature is currently available only on Essentials plans or higher.

Security-requested version bumps:
- next: 16.2.6 -> 16.3.3 (pin lockfile version explicitly)
- eslint: ^9 -> ^10 (resolves to 10.9.1)

eslint-plugin-react@7.37.5 calls context.getFilename() which was removed
in ESLint 10. Workaround: pin settings.react.version = '19.2.4' in
eslint.config.mjs to skip the auto-detection code path that hits the
removed API. Tracked upstream: jsx-eslint/eslint-plugin-react#3977

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Free

Run ID: 90574dc2-1e68-49c4-acba-da27db1dddba

📥 Commits

Reviewing files that changed from the base of the PR and between 5364f6f and 266d9c3.

⛔ Files ignored due to path filters (1)
  • pointer/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • pointer/eslint.config.mjs
  • pointer/package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Walkthrough

The PR updates Next.js and ESLint versions. It also pins React 19.2.4 in the ESLint configuration.

Changes

Frontend tooling updates

Layer / File(s) Summary
Tooling versions and lint configuration
pointer/package.json, pointer/eslint.config.mjs
Next.js changes from 16.2.6 to 16.3.3. ESLint changes from ^9 to ^10. The ESLint React setting pins React to 19.2.4.

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


Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

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

@snyk-io

snyk-io Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues
✅ Secrets 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cb-alish
cb-alish merged commit d5301ad into main Sep 10, 2026
7 checks passed
@cb-alish
cb-alish deleted the bump/next-eslint-security branch September 10, 2026 06:45
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