build(deps-dev): bump eslint-plugin-jsdoc from 63.3.3 to 64.3.1 - #1138
Open
dependabot[bot] wants to merge 1 commit into
Open
build(deps-dev): bump eslint-plugin-jsdoc from 63.3.3 to 64.3.1#1138dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) from 63.3.3 to 64.3.1. - [Release notes](https://github.com/gajus/eslint-plugin-jsdoc/releases) - [Commits](gajus/eslint-plugin-jsdoc@v63.3.3...v64.3.1) --- updated-dependencies: - dependency-name: eslint-plugin-jsdoc dependency-version: 64.3.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
Devin Review found 2 potential issues.
⚠️ 1 issue in files not directly in the diff
⚠️ Lockfile provenance checks always fail
Every platform-specific @esbuild/* record loses peer: true. Both lockfile provenance gates now fail before CI can accept this update.
| "devDependencies": { | ||
| "@eslint/js": "^10.0.1", | ||
| "eslint-plugin-jsdoc": "^63.0.13", | ||
| "eslint-plugin-jsdoc": "^64.3.1", |
There was a problem hiding this comment.
🟡 Supported Node versions lose lint
On Node 22.13–22.22.1, eslint-plugin-jsdoc@64.3.1 rejects the project's supported runtime range. Those installations no longer have a supported lint stack.
Prompt for agents
Align the eslint-plugin-jsdoc upgrade with BandScope's Node compatibility contract. Version 64.3.1 and its @es-joy/jsdoccomment dependency require Node 22.22.2 or newer, while package.json and the repository's toolchain contract continue to support Node >=22.13 <23. Either select a plugin release compatible with the existing floor or perform the separately coordinated Node-floor migration, including manifest, tests, documentation, and CI compatibility coverage.
Was this helpful? React with 👍 or 👎 to provide feedback.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps eslint-plugin-jsdoc from 63.3.3 to 64.3.1.
Release notes
Sourced from eslint-plugin-jsdoc's releases.
... (truncated)
Commits
7447620fix(no-unnecessary-type-assertion): avoid multiple warnings when typescript...4be7b47feat(no-unnecessary-type-assertion): add rule for checking@typeassertionsdc99c3cfix: update jsdcoccomment, devDeps (#1746)8a37bd2feat(check-param-names): add order fixer and suggestions (#1732)7309d7dfeat: update jsdoccomment, devDeps.; use nodenext for module properties in TS4de1b19chore: update jsdoccomment, devDep.fbe2a2bfix: update jsdoccomment and devDep.343516afix: resume support for CJS via require(esm)7e94c04chore: update jsdoccomment, comment-parser, devDeps.9c9b723feat: ESM only; fixes #1626Dependabot 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)