Skip to content

Bump eslint from 9.31.0 to 9.32.0 #1573

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

Merged
merged 1 commit into from
Jul 28, 2025

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 28, 2025

Bumps eslint from 9.31.0 to 9.32.0.

Release notes

Sourced from eslint's releases.

v9.32.0

Features

  • 1245000 feat: support explicit resource management in core rules (#19828) (fnx)
  • 0e957a7 feat: support typescript types in accessor rules (#19882) (fnx)

Bug Fixes

  • 960fd40 fix: Upgrade @​eslint/js (#19971) (Nicholas C. Zakas)
  • bbf23fa fix: Refactor reporting into FileReport (#19877) (Nicholas C. Zakas)
  • d498887 fix: bump @​eslint/plugin-kit to 0.3.4 to resolve vulnerability (#19965) (Milos Djermanovic)
  • f46fc6c fix: report only global references in no-implied-eval (#19932) (Nitin Kumar)
  • 7863d26 fix: remove outdated types in ParserOptions.ecmaFeatures (#19944) (ntnyq)
  • 3173305 fix: update execScript message in no-implied-eval rule (#19937) (TKDev7)

Documentation

  • 86e7426 docs: Update README (GitHub Actions Bot)

Chores

  • 50de1ce chore: package.json update for @​eslint/js release (Jenkins)
  • 74f01a3 ci: unpin jiti to version ^2.5.1 (#19970) (루밀LuMir)
  • 2ab1381 ci: pin jiti to version 2.4.2 (#19964) (Francesco Trotta)
  • b7f7545 test: switch to flat config mode in SourceCode tests (#19953) (Milos Djermanovic)
  • f5a35e3 test: switch to flat config mode in eslint-fuzzer (#19960) (Milos Djermanovic)
  • e22af8c refactor: use CustomRuleDefinitionType in JSRuleDefinition (#19949) (Francesco Trotta)
  • e855717 chore: switch performance tests to hyperfine (#19919) (Francesco Trotta)
  • 2f73a23 test: switch to flat config mode in ast-utils tests (#19948) (Milos Djermanovic)
  • c565a53 chore: exclude further_reading_links.json from Prettier formatting (#19943) (Milos Djermanovic)
Changelog

Sourced from eslint's changelog.

v9.32.0 - July 25, 2025

  • 960fd40 fix: Upgrade @​eslint/js (#19971) (Nicholas C. Zakas)
  • 50de1ce chore: package.json update for @​eslint/js release (Jenkins)
  • bbf23fa fix: Refactor reporting into FileReport (#19877) (Nicholas C. Zakas)
  • 74f01a3 ci: unpin jiti to version ^2.5.1 (#19970) (루밀LuMir)
  • d498887 fix: bump @​eslint/plugin-kit to 0.3.4 to resolve vulnerability (#19965) (Milos Djermanovic)
  • 2ab1381 ci: pin jiti to version 2.4.2 (#19964) (Francesco Trotta)
  • b7f7545 test: switch to flat config mode in SourceCode tests (#19953) (Milos Djermanovic)
  • f5a35e3 test: switch to flat config mode in eslint-fuzzer (#19960) (Milos Djermanovic)
  • f46fc6c fix: report only global references in no-implied-eval (#19932) (Nitin Kumar)
  • 86e7426 docs: Update README (GitHub Actions Bot)
  • e22af8c refactor: use CustomRuleDefinitionType in JSRuleDefinition (#19949) (Francesco Trotta)
  • 1245000 feat: support explicit resource management in core rules (#19828) (fnx)
  • e855717 chore: switch performance tests to hyperfine (#19919) (Francesco Trotta)
  • 0e957a7 feat: support typescript types in accessor rules (#19882) (fnx)
  • 2f73a23 test: switch to flat config mode in ast-utils tests (#19948) (Milos Djermanovic)
  • 7863d26 fix: remove outdated types in ParserOptions.ecmaFeatures (#19944) (ntnyq)
  • c565a53 chore: exclude further_reading_links.json from Prettier formatting (#19943) (Milos Djermanovic)
  • 3173305 fix: update execScript message in no-implied-eval rule (#19937) (TKDev7)
Commits

Dependabot compatibility score

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)

Bumps [eslint](https://github.com/eslint/eslint) from 9.31.0 to 9.32.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
- [Commits](eslint/eslint@v9.31.0...v9.32.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-version: 9.32.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Changes to the project's dependencies label Jul 28, 2025
Copy link

Software Supply Chain Report of ericcornelissen/eslint-plugin-top - d96f33ed91aecb

How to read the results 📖

Dirty-waters has analyzed your project dependencies and found different categories for each of them:

  • ⚠️⚠️⚠️ : high severity

  • ⚠️⚠️: medium severity

  • ⚠️: low severity

Total packages in the supply chain: 21

🔒 Packages with signature changes (⚠️⚠️⚠️): 0

❗ Downgraded packages (⚠️⚠️): 20

👽 Commits made by both New Authors and Reviewers (⚠️⚠️): 0

🙈 Commits approved by New Reviewers (⚠️⚠️): 0

😐 Commits made by New Authors (⚠️): 0

Fine grained information

🐬 For further information about software supply chain smells in your project, take a look at the following tables.

❗ Downgraded packages (⚠️⚠️) (20)
package_name repo_link category old_version new_version
@inquirer/prompts https://github.com/sboudrias/inquirer.js Downgraded package 7.7.1 7.6.0
source-map https://github.com/mozilla/source-map Downgraded package 0.7.6 0.7.4
@inquirer/select https://github.com/sboudrias/inquirer.js Downgraded package 4.3.1 4.2.4
@babel/types https://github.com/babel/babel Downgraded package 7.28.2 7.28.1
@inquirer/search https://github.com/sboudrias/inquirer.js Downgraded package 3.0.17 3.0.16
validate-npm-package-name https://github.com/npm/validate-npm-package-name Downgraded package 6.0.2 6.0.1
@inquirer/core https://github.com/sboudrias/inquirer.js Downgraded package 10.1.15 10.1.14
@inquirer/editor https://github.com/sboudrias/inquirer.js Downgraded package 4.2.15 4.2.14
@inquirer/number https://github.com/sboudrias/inquirer.js Downgraded package 3.0.17 3.0.16
@inquirer/password https://github.com/sboudrias/inquirer.js Downgraded package 4.0.17 4.0.16
@inquirer/checkbox https://github.com/sboudrias/inquirer.js Downgraded package 4.2.0 4.1.9
@inquirer/type https://github.com/sboudrias/inquirer.js Downgraded package 3.0.8 3.0.7
electron-to-chromium https://github.com/kilian/electron-to-chromium Downgraded package 1.5.191 1.5.187
@inquirer/input https://github.com/sboudrias/inquirer.js Downgraded package 4.2.1 4.2.0
@inquirer/figures https://github.com/sboudrias/inquirer.js Downgraded package 1.0.13 1.0.12
@babel/helpers https://github.com/babel/babel Downgraded package 7.28.2 7.27.6
@inquirer/expand https://github.com/sboudrias/inquirer.js Downgraded package 4.0.17 4.0.16
@inquirer/rawlist https://github.com/sboudrias/inquirer.js Downgraded package 4.1.5 4.1.4
@types/node https://github.com/definitelytyped/definitelytyped Downgraded package 24.1.0 24.0.15
@inquirer/confirm https://github.com/sboudrias/inquirer.js Downgraded package 5.1.14 5.1.13

Call to Action:

👻What do I do now?

For packages with signature changes:

  • Why? Changes in code signatures could indicate tampering with the package or compromised build processes, potentially introducing malicious code.
  1. This means that a dependency either had code signature and now does not, or that the signature was valid and now it's not.
  2. This could be a security risk, and you should halt the project until you can verify the changes.

For downgraded dependencies:

  • Why? Downgrading packages may reintroduce known security vulnerabilities that were fixed in newer versions.
  1. Check the release notes of the new version to see if the downgrade is intentional. If the new version is more than one release ahead, verify whether any breaking changes in between apply to your project.
  2. If the downgrade is unintentional, consider updating the package to a version that is compatible with your project.

For commits made by both new authors and reviewers:

  • Why? When both authors and reviewers are new to a project, there's a higher risk of malicious code being introduced due to lack of established trust and project knowledge.
  1. Verify, as best as you can, that the new authors and reviewers are not malicious actors.
  2. If you are unsure, consider reverting the changes.

For commits approved by new reviewers:

  • Why? New reviewers may not be familiar with the project's security requirements or may not have the expertise to identify malicious code.
  1. Verify, as best as you can, that the new reviewers are not malicious actors.

For commits made by new authors:

  • Why? New contributors could potentially introduce security vulnerabilities, either accidentally or intentionally.
  1. Verify, as best as you can, that the new authors are not malicious actors.
  2. The fact that the reviewers are not new to the repository is a good sign.
---

Report created by dirty-waters.

Report created on 2025-07-28 07:10:47

  • Tool version: 6379805f
  • Project Name: ericcornelissen/eslint-plugin-top
  • Compared project versions: d96f33e & d91aecb

@ericcornelissen ericcornelissen merged commit 64917b9 into main Jul 28, 2025
27 of 29 checks passed
@ericcornelissen ericcornelissen deleted the dependabot/npm_and_yarn/eslint-9.32.0 branch July 28, 2025 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Changes to the project's dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant