🔒 [Security](deps-dev): bump eslint-config-next from 16.1.1 to 16.2.1#148
🔒 [Security](deps-dev): bump eslint-config-next from 16.1.1 to 16.2.1#148dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) from 16.1.1 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](https://github.com/vercel/next.js/commits/v16.2.1/packages/eslint-config-next) --- updated-dependencies: - dependency-name: eslint-config-next dependency-version: 16.2.1 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Deploying blackroad-os-web with
|
| Latest commit: |
5994daa
|
| Status: | 🚫 Build failed. |
![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: 5994daa4d1
ℹ️ 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".
| "@types/react-dom": "^19", | ||
| "eslint": "^9", | ||
| "eslint-config-next": "16.1.1", | ||
| "eslint-config-next": "16.2.1", |
There was a problem hiding this comment.
eslint-config-next aligned with next
package.json now pins eslint-config-next to 16.2.1 while the app still runs next 16.1.1 (package.json:15). This repo’s eslint.config.mjs imports eslint-config-next/core-web-vitals and eslint-config-next/typescript, and CI runs npm run lint in .github/workflows/ci.yml, so every PR will lint against a different Next.js release than the one we actually ship. Next’s own upgrade guidance calls out keeping these versions the same; otherwise rule/parser changes in 16.2.x can introduce false positives or miss issues for a 16.1.x app.
Useful? React with 👍 / 👎.
Bumps eslint-config-next from 16.1.1 to 16.2.1.
Release notes
Sourced from eslint-config-next's releases.
... (truncated)
Commits
ed7d2cev16.2.1c5c94dfv16.2.03683192v16.2.0-canary.1046689814v16.2.0-canary.103ad66dbcv16.2.0-canary.102b856498v16.2.0-canary.101136b77ev16.2.0-canary.1000f59973v16.2.0-canary.99792522dv16.2.0-canary.982769b55v16.2.0-canary.97Dependabot 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)