Skip to content

deps: update dependency eslint to v10#7

Open
renovate[bot] wants to merge 1 commit intomainfrom
deps/major-eslint-monorepo
Open

deps: update dependency eslint to v10#7
renovate[bot] wants to merge 1 commit intomainfrom
deps/major-eslint-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint (source) 9.39.310.0.2 age confidence

Release Notes

eslint/eslint (eslint)

v10.0.2

Compare Source

v10.0.1

Compare Source

Bug Fixes

Documentation

  • 5b3dbce docs: add AI acknowledgement section to templates (#​20431) (루밀LuMir)
  • 6f23076 docs: toggle nav in no-JS mode (#​20476) (Tanuj Kanti)
  • b69cfb3 docs: Update README (GitHub Actions Bot)

Chores

v10.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10:00 before 18:00 every weekday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the deps Update dependencies label Feb 27, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 27, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 158, reused 0, downloaded 0, added 0
Progress: resolved 304, reused 0, downloaded 0, added 0
Progress: resolved 376, reused 0, downloaded 0, added 0
Progress: resolved 423, reused 0, downloaded 0, added 0
Progress: resolved 433, reused 0, downloaded 0, added 0
Progress: resolved 433, reused 0, downloaded 0, added 0, done
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
├─┬ @praha/eslint-config-common 4.0.3
│ ├── ✕ unmet peer eslint@^9.0.0: found 10.0.2
│ └─┬ @praha/eslint-config-definer 2.0.2
│   └── ✕ unmet peer eslint@^9.0.0: found 10.0.2
├─┬ @praha/eslint-config-javascript 3.0.11
│ ├── ✕ unmet peer eslint@^9.0.0: found 10.0.2
│ └─┬ eslint-plugin-import-x 4.16.1
│   └── ✕ unmet peer eslint@"^8.57.0 || ^9.0.0": found 10.0.2
├─┬ @praha/eslint-config-typescript 3.0.12
│ └── ✕ unmet peer eslint@^9.0.0: found 10.0.2
└─┬ @praha/eslint-config-style 3.0.12
  └── ✕ unmet peer eslint@^9.0.0: found 10.0.2
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false



@changeset-bot
Copy link

changeset-bot bot commented Feb 27, 2026

⚠️ No Changeset found

Latest commit: 5633638

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the deps/major-eslint-monorepo branch 2 times, most recently from f569269 to 89276d0 Compare February 27, 2026 02:19
@renovate renovate bot force-pushed the deps/major-eslint-monorepo branch from 89276d0 to 5633638 Compare February 27, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deps Update dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants