Bump the npm-development group across 1 directory with 2 updates#24
Bump the npm-development group across 1 directory with 2 updates#24dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps the npm-development group with 1 update in the / directory: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin). Updates `@typescript-eslint/eslint-plugin` from 8.57.1 to 8.57.2 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.57.2/packages/eslint-plugin) Updates `@typescript-eslint/parser` from 8.57.1 to 8.57.2 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.57.2/packages/parser) --- updated-dependencies: - dependency-name: "@typescript-eslint/eslint-plugin" dependency-version: 8.57.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-development - dependency-name: "@typescript-eslint/parser" dependency-version: 8.57.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| "@types/jest": "^30.0.0", | ||
| "@types/node": "^25.5.0", | ||
| "@typescript-eslint/eslint-plugin": "^8.57.1", | ||
| "@typescript-eslint/eslint-plugin": "^8.57.2", |
There was a problem hiding this comment.
Parser version not bumped to match plugin peer dependency
Low Severity
@typescript-eslint/parser in package.json remains at ^8.57.1, but the updated @typescript-eslint/eslint-plugin@8.57.2 declares a peer dependency of @typescript-eslint/parser: "^8.57.2" (requiring >=8.57.2). While the lockfile currently resolves the parser to 8.57.2, a fresh install or CI environment could resolve it to 8.57.1, causing a peer dependency conflict or warning. The parser version spec needs to be bumped to ^8.57.2 to stay consistent.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="package.json">
<violation number="1" location="package.json:57">
P2: `@typescript-eslint/parser` should be bumped to `^8.57.2` to match the peer dependency declared by `@typescript-eslint/eslint-plugin@8.57.2`. The current `^8.57.1` range could resolve to `8.57.1` in a fresh install, which would not satisfy the plugin's `^8.57.2` peer requirement and produce warnings or errors.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "@types/jest": "^30.0.0", | ||
| "@types/node": "^25.5.0", | ||
| "@typescript-eslint/eslint-plugin": "^8.57.1", | ||
| "@typescript-eslint/eslint-plugin": "^8.57.2", |
There was a problem hiding this comment.
P2: @typescript-eslint/parser should be bumped to ^8.57.2 to match the peer dependency declared by @typescript-eslint/eslint-plugin@8.57.2. The current ^8.57.1 range could resolve to 8.57.1 in a fresh install, which would not satisfy the plugin's ^8.57.2 peer requirement and produce warnings or errors.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 57:
<comment>`@typescript-eslint/parser` should be bumped to `^8.57.2` to match the peer dependency declared by `@typescript-eslint/eslint-plugin@8.57.2`. The current `^8.57.1` range could resolve to `8.57.1` in a fresh install, which would not satisfy the plugin's `^8.57.2` peer requirement and produce warnings or errors.</comment>
<file context>
@@ -54,7 +54,7 @@
"@types/jest": "^30.0.0",
"@types/node": "^25.5.0",
- "@typescript-eslint/eslint-plugin": "^8.57.1",
+ "@typescript-eslint/eslint-plugin": "^8.57.2",
"@typescript-eslint/parser": "^8.57.1",
"eslint": "^10.1.0",
</file context>
Bumps the npm-development group with 1 update in the / directory: @typescript-eslint/eslint-plugin.
Updates
@typescript-eslint/eslint-pluginfrom 8.57.1 to 8.57.2Release notes
Sourced from
@typescript-eslint/eslint-plugin's releases.Changelog
Sourced from
@typescript-eslint/eslint-plugin's changelog.Commits
be4d54dchore(release): publish 8.57.2f68c8e4fix(eslint-plugin): [prefer-readonly-parameter-types] preserve type alias inf...73acd2efix(eslint-plugin): [no-useless-default-assignment] skip reporting false posi...3d21482fix(eslint-plugin): [no-unsafe-return] false positive on unwrapping generic (...e128548fix(eslint-plugin): [no-restricted-types] flag banned generics in extends or ...2b7f63fchore(eslint-plugin): correct tsutils.isTypeFlag usage post-merge65175cdfix(eslint-plugin): [array-type] ignore Array and ReadonlyArray without type ...9c9ab5efeat(eslint-plugin): [no-unnecessary-type-arguments] report inferred required...42a1c89fix(eslint-plugin): [prefer-optional-chain] remove dangling closing parenthes...71855ffdocs(eslint-plugin): [no-unnecessary-condition] add link to TS handbook (#12131)Updates
@typescript-eslint/parserfrom 8.57.1 to 8.57.2Release notes
Sourced from
@typescript-eslint/parser's releases.Changelog
Sourced from
@typescript-eslint/parser's changelog.Commits
be4d54dchore(release): publish 8.57.2Dependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions