-
Notifications
You must be signed in to change notification settings - Fork 96
chore(deps-dev): bump eslint from 8.57.1 to 9.26.0 #8769
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: main
Are you sure you want to change the base?
Conversation
Bumps [eslint](https://github.com/eslint/eslint) from 8.57.1 to 9.26.0. - [Release notes](https://github.com/eslint/eslint/releases) - [Changelog](https://github.com/eslint/eslint/blob/v9.26.0/CHANGELOG.md) - [Commits](eslint/eslint@v8.57.1...v9.26.0) --- updated-dependencies: - dependency-name: eslint dependency-version: 9.26.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
🤖 AI PR Validation ReportPR Review ResultsThank you for your submission! Here's detailed feedback on your PR title and body compliance:✅ PR Title
✅ Commit Type
❌ Risk Level
❌ What & Why
❌ Impact of Change
❌ Test Plan
|
| Section | Status | Recommendation |
|---|---|---|
| Title | ✅ | Keep as-is. |
| Commit Type | ✅ | Correct (chore). |
| Risk Level | ❌ | Add risk:medium label and Risk Level section in body with rationale. |
| What & Why | ❌ | Add a 1–2 sentence summary of what changed and why (see example above). |
| Impact of Change | ❌ | Add Impact bullets for Users / Developers / System mentioning Node/CI impact and lint changes. |
| Test Plan | ❌ | Add explicit test steps (install, lint, unit/E2E, CI), and link to CI run(s). CI must pass before merge. |
| Contributors | Optional: add reviewers/credits if applicable. | |
| Screenshots/Videos | N/A for this PR. |
Final notes & next steps
- Advised risk level: risk:medium. The PR currently lacks a risk label and the required template sections; please add the
risk:mediumlabel and update the PR body to include the the "What & Why", "Impact of Change", and "Test Plan" fields from the repo template. - Verify CI Node version: the lockfile changes include packages with Node engine constraints >=18.18.0 for many ESLint-related packages. Ensure CI is running a compatible Node version (or explicitly document that you tested compatibility and what changed). If CI uses Node 16 or 18 lower than required, update the CI image or provide a compatibility mitigation.
- Run and document the following before merging:
pnpm install --frozen-lockfile(or repo's package manager command) — ensure it succeeds.pnpm lintand fix or document lint rule changes (or schedule a follow-up to fix lint failures). Attach output or link to a successful CI run.pnpm test(unit tests) and link to passing results.
- If this PR is intended to be auto-merged after CI, note that in the body (Dependabot instructions are present but still include your test expectations).
Please update the PR body using the template fields and add the risk:medium label. After updating, run CI and paste the relevant successful CI run link or logs into the Test Plan section. Once those are present and CI is green, this PR should be safe to merge.
Thank you!
Last updated: Fri, 30 Jan 2026 23:28:28 GMT
|
📊 Coverage check completed. See workflow run for details. |
Bumps eslint from 8.57.1 to 9.26.0.
Release notes
Sourced from eslint's releases.
... (truncated)
Changelog
Sourced from eslint's changelog.
... (truncated)
Commits
8bbabc49.26.016f5ff7Build: changelog update for 9.26.05b247c8chore: upgrade to@eslint/js@9.26.0(#19681)d6fa4acchore: package.json update for@eslint/jsreleasee9754e7feat: add reportGlobalThis to no-shadow-restricted-names (#19670)0fa2b7afeat: add suggestions foreqeqeqrule (#19640)dd98d63docs: Update README96e84defix: check cache file existence before deletion (#19648)c25e858docs: Update README0958690chore: disambiguate internal typesLanguageOptionsandRule(#19669)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)You can disable automated security fix PRs for this repo from the Security Alerts page.