-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps-dev): bump eslint-plugin-github from 4.10.2 to 6.0.0 #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
chore(deps-dev): bump eslint-plugin-github from 4.10.2 to 6.0.0 #4
Conversation
Bumps [eslint-plugin-github](https://github.com/github/eslint-plugin-github) from 4.10.2 to 6.0.0. - [Release notes](https://github.com/github/eslint-plugin-github/releases) - [Commits](github/eslint-plugin-github@v4.10.2...v6.0.0) --- updated-dependencies: - dependency-name: eslint-plugin-github dependency-version: 6.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dce1f74
to
5c02348
Compare
WalkthroughThis update focuses on upgrading the eslint-plugin-github dependency from v4.10.2 to v6.0.0. The major version change introduces ESM-only format and requires Node.js 20.x+. The upgrade includes significant updates to core dependencies like TypeScript, Prettier, and ESLint-related packages, along with enhanced security patches and compatibility improvements. Changes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Files selected (2)
- package.json (1)
- pnpm-lock.yaml (71)
Review comments generated (5)
- Review: 4
- LGTM: 1
[email protected]: | ||
resolution: {integrity: sha512-ypowyDxpVSYpkXr9WPv2PAZCtNip1Mv5KTW0SCurXv/9iOpcrH9PaqUElksqEB6pChqHGDRCFTyrZlGhnLNGiA==} | ||
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0} | ||
deprecated: This version is no longer supported. Please see https://eslint.org/version-support for other options. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version of ESLint being used (8.57.1) is marked as deprecated with a warning message. This could lead to future compatibility issues and security vulnerabilities.
- [email protected]:
+ # Consider upgrading to a supported ESLint version per https://eslint.org/version-support
eslint-plugin-filenames: 1.3.2([email protected]) | ||
eslint-plugin-i18n-text: 1.0.1([email protected]) | ||
eslint-plugin-import: 2.31.0(@typescript-eslint/parser@7.18.0([email protected])(typescript@4.9.5))([email protected]) | ||
eslint-plugin-import: 2.31.0(@typescript-eslint/parser@8.41.0([email protected])(typescript@5.9.2))([email protected]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
prettier: 3.5.3 | ||
prettier: 3.6.2 | ||
svg-element-attributes: 1.3.1 | ||
typescript: 5.9.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eslint: 8.57.1 | ||
typescript: 5.9.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The typescript-eslint package has both ESLint and TypeScript as direct dependencies which could cause version conflicts with the project's peer dependencies.
The rest of the changes appear to be routine dependency updates and version synchronization changes that don't present critical issues.
Bumps eslint-plugin-github from 4.10.2 to 6.0.0.
Release notes
Sourced from eslint-plugin-github's releases.
... (truncated)
Commits
139bf63
Merge pull request #622 from 43081j/esm-onlyba655ea
Merge branch 'main' into esm-only88ccca2
Merge pull request #621 from 43081j/meta-lints2174e40
feat: move to esm-onlydef8cea
chore: update rule meta to satisfiy lint rules4832156
Merge pull request #620 from github/dependabot/npm_and_yarn/all-dependencies-...c613603
chore(deps): bump the all-dependencies group with 4 updates83669fa
chore(deps): bump the all-dependencies group with 8 updates (#619)632d445
chore(deps): bump eslint-config-prettier in the all-dependencies group (#618)ea508d2
Merge pull request #617 from github/dependabot/npm_and_yarn/all-dependencies-...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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Release Notes
Chore:
This update improves security and compatibility with modern JavaScript tooling. Users on Node.js versions below 20.x should continue using eslint-plugin-github v5.x until they can upgrade their Node.js environment.