Bump next from 16.1.7 to 16.2.1 in /apps/web#40
Conversation
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9488db4a61
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "clsx": "^2.1.1", | ||
| "lucide-react": "^0.577.0", | ||
| "next": "16.1.7", | ||
| "next": "16.2.1", |
There was a problem hiding this comment.
Because apps/web/eslint.config.mjs imports eslint-config-next/core-web-vitals and eslint-config-next/typescript, bumping only next here leaves the app on next@16.2.1 while the lint config and @next/eslint-plugin-next stay on 16.1.6. Next’s upgrade guidance explicitly upgrades eslint-config-next alongside next, so after this change npm run lint will still enforce the 16.1 ruleset and can miss or misreport 16.2-specific issues in this app.
Useful? React with 👍 / 👎.
Bumps [next](https://github.com/vercel/next.js) from 16.1.7 to 16.2.1. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.1.7...v16.2.1) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/apps/web/next-16.2.1
branch
from
9488db4 to
0fb856e
Compare
Bumps next from 16.1.7 to 16.2.1.
Release notes
Sourced from next's releases.
... (truncated)
Commits
ed7d2cev16.2.13e37bb4docs: post release amends (#91715)a15ec6edocs: fix broken Activity Patterns demo link in preserving UI state guide (#9...600cd2fFix adapter outputs for dynamic metadata routes (#91680)27886d3Turbopack: fix webpack loader runner layer (#91727)88fc430Fix server actions in standalone mode withcacheComponents(#91711)37aed86turbo-persistence: remove Unmergeable mmap advice (#91713)d6195ecFix layout segment optimization: move app-page imports to server-utility tran...6cb97d6Turbopack: lazy require metadata and handle TLA (#91705)e6b101a[turbopack] Respect{eval:true}in worker_threads constructors (#91666)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)