You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This upgrade contains major breaking changes across all three core packages, requiring significant configuration and code modifications. The primary drivers are ESLint's new configuration format and Next.js's evolution from version 13 through 15, including the adoption of React 19.
eslint 8.45.0 → 9.26.0: This is a high-risk upgrade. ESLint 9 introduces a new "flat" configuration file (eslint.config.js) by default, deprecating the legacy .eslintrc format. This requires a full migration of your configuration, including how plugins are imported and rules are defined. Additionally, it drops support for Node.js versions below 18.18.0 and removes several core formatters and rules.
next 13.4.12 → 15.5.10: This is a high-risk upgrade. The jump from version 13 to 15 spans multiple major releases and incorporates breaking changes from React 19. Key changes include the deprecation of useFormState in favor of useActionState and making previously synchronous APIs for accessing cookies, headers, and route params asynchronous. The minimum required Node.js version is also increased.
eslint-config-next 13.4.12 → 15.0.0: This is a medium-risk upgrade. The breaking changes are a direct result of the updates in ESLint and Next.js. The configuration is updated to be compatible with ESLint 9's flat config format and the new rules and APIs available in Next.js 15. Manual validation will be required after migrating the other two packages.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
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
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.
Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.
Snyk changed the following file(s):
usage-based-subscriptions/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NEXT-15104645
SNYK-JS-ESLINT-15102420
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling