This repository was archived by the owner on Dec 22, 2025. It is now read-only.
Update all of eslint 9.37.0 → 9.38.0 (minor)#444
Merged
depfu[bot] merged 1 commit intomasterfrom Oct 18, 2025
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @eslint/js (9.37.0 → 9.38.0) · Repo · Changelog
Release Notes
9.38.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
9.38.0Build: changelog update for 9.38.0chore: upgrade @eslint/js@9.38.0 (#20221)chore: package.json update for @eslint/js releasefix: improve type support for isolated dependencies in pnpm (#20201)refactor: Use types from @eslint/core (#20168)ci: add Node.js 25 to `ci.yml` (#20220)feat: update `complexity` rule to only highlight function header (#20048)feat: correct `no-loss-of-precision` false positives with `e` notation (#20187)ci: bump github/codeql-action from 3 to 4 (#20211)test: remove use of `nodejsScope` option of eslint-scope from tests (#20206)docs: improve web accessibility by hiding non-semantic character (#20205)docs: correct formatting in `no-irregular-whitespace` rule documentation (#20203)docs: Update READMEchore: fix typo in legacy-eslint.js (#20202)chore: fix typos (#20200)fix: correct SourceCode typings (#20114)chore: use team member's username when name is not available in data (#20194)docs: move `custom-formatters` type descriptions to `nodejs-api` (#20190)chore: mark deprecated rules as available until v11.0.0 (#20184)✳️ eslint (9.37.0 → 9.38.0) · Repo · Changelog
Release Notes
9.38.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
9.38.0Build: changelog update for 9.38.0chore: upgrade @eslint/js@9.38.0 (#20221)chore: package.json update for @eslint/js releasefix: improve type support for isolated dependencies in pnpm (#20201)refactor: Use types from @eslint/core (#20168)ci: add Node.js 25 to `ci.yml` (#20220)feat: update `complexity` rule to only highlight function header (#20048)feat: correct `no-loss-of-precision` false positives with `e` notation (#20187)ci: bump github/codeql-action from 3 to 4 (#20211)test: remove use of `nodejsScope` option of eslint-scope from tests (#20206)docs: improve web accessibility by hiding non-semantic character (#20205)docs: correct formatting in `no-irregular-whitespace` rule documentation (#20203)docs: Update READMEchore: fix typo in legacy-eslint.js (#20202)chore: fix typos (#20200)fix: correct SourceCode typings (#20114)chore: use team member's username when name is not available in data (#20194)docs: move `custom-formatters` type descriptions to `nodejs-api` (#20190)chore: mark deprecated rules as available until v11.0.0 (#20184)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands