Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2025

This PR contains the following updates:

Package Change Age Confidence
eslint-scope (source) ^8.4.0 -> ^9.0.0 age confidence

Release Notes

eslint/js (eslint-scope)

v9.0.0

Compare Source

⚠ BREAKING CHANGES
  • Resolve references to global var/function, add addGlobals() (#​682)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#​696)
Features
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#​696) (9c84ecb)
  • Resolve references to global var/function, add addGlobals() (#​682) (f007b46)
Dependencies
  • The following workspace dependencies were updated
    • devDependencies
      • eslint-visitor-keys bumped from ^4.2.1 to ^5.0.0
      • espree bumped from ^10.4.0 to ^11.0.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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
Copy link
Contributor Author

renovate bot commented Nov 11, 2025

⚠️ 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
Scope: all 3 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
docs-svelte-kit                          |  WARN  deprecated @types/eslint-visitor-keys@3.3.2
.                                        |  WARN  deprecated eslint-plugin-markdown@5.1.0
/tmp/renovate/repos/github/sveltejs/eslint-plugin-svelte/docs-svelte-kit:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for eslint-scope@^9.0.0 published by Mon Nov 10 2025 06:37:12 GMT+0000 (Coordinated Universal Time) while fetching it from https://registry.npmjs.org/. Version 9.0.0 satisfies the specs but was released at Mon Nov 10 2025 16:30:18 GMT+0000 (Coordinated Universal Time)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/sveltejs/eslint-plugin-svelte/docs-svelte-kit

The latest release of eslint-scope is "9.0.0". Published at 11/10/2025 4:30:18 PM

Other releases are:
  * next: 4.0.0-rc.0 published at 6/9/2018
  * v3-latest: 3.7.3 published at 7/12/2018

If you need the full list of all 27 published versions run "$ pnpm view eslint-scope versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

@changeset-bot
Copy link

changeset-bot bot commented Nov 11, 2025

⚠️ No Changeset found

Latest commit: a388dbd

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 renovate/eslint-scope-9.x branch from 59f943e to a388dbd Compare November 11, 2025 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant