Skip to content

Update dependency @eslint/compat to v2#114

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-compat-2.x
Open

Update dependency @eslint/compat to v2#114
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/eslint-compat-2.x

Conversation

@renovate

@renovate renovate Bot commented Feb 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@eslint/compat (source) ^1.3.0^2.0.0 age confidence

Release Notes

eslint/rewrite (@​eslint/compat)

v2.1.0

Compare Source

Features

v2.0.5

Compare Source

Dependencies
  • The following workspace dependencies were updated

v2.0.4

Compare Source

Dependencies
  • The following workspace dependencies were updated

v2.0.3

Compare Source

Dependencies
  • The following workspace dependencies were updated

v2.0.2

Compare Source

Bug Fixes
Dependencies
  • The following workspace dependencies were updated

v2.0.1

Compare Source

Dependencies
  • The following workspace dependencies were updated

v2.0.0

Compare Source

⚠ BREAKING CHANGES
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#​297)
Features
Dependencies
  • The following workspace dependencies were updated

v1.4.1

Compare Source

Dependencies
  • The following workspace dependencies were updated

v1.4.0

Compare Source

Features
Dependencies
  • The following workspace dependencies were updated

v1.3.2

Compare Source

Dependencies
  • The following workspace dependencies were updated

v1.3.1

Compare Source

Bug Fixes
  • relax @eslint/compat eslint peerDependencies constraint (#​215) (b96ec0c)
Dependencies
  • The following workspace dependencies were updated

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR becomes conflicted, 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 force-pushed the renovate/eslint-compat-2.x branch from 63db963 to 96cf4c3 Compare March 6, 2026 22:35
@renovate renovate Bot force-pushed the renovate/eslint-compat-2.x branch 2 times, most recently from 0ddd991 to 82f51be Compare April 8, 2026 09:54
@renovate renovate Bot force-pushed the renovate/eslint-compat-2.x branch 2 times, most recently from 77084c6 to c109744 Compare May 12, 2026 17:08
@renovate renovate Bot force-pushed the renovate/eslint-compat-2.x branch from c109744 to 4fd5435 Compare June 11, 2026 14:59
@renovate renovate Bot force-pushed the renovate/eslint-compat-2.x branch from 4fd5435 to 7e84247 Compare July 12, 2026 12:42
@renovate

renovate Bot commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 2 workspace projects
? Verifying lockfile against supply-chain policies (882 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 80, reused 0, downloaded 0, added 0
Progress: resolved 90, reused 0, downloaded 1, added 0
Progress: resolved 227, reused 0, downloaded 1, added 0
Progress: resolved 328, reused 0, downloaded 1, added 0
Progress: resolved 351, reused 0, downloaded 1, added 0
Progress: resolved 352, reused 0, downloaded 1, added 0
Progress: resolved 354, reused 0, downloaded 1, added 0
Progress: resolved 355, reused 0, downloaded 1, added 0
Progress: resolved 356, reused 0, downloaded 1, added 0
Progress: resolved 359, reused 0, downloaded 1, added 0
Progress: resolved 410, reused 0, downloaded 1, added 0
Progress: resolved 638, reused 0, downloaded 1, added 0
✗ Lockfile failed supply-chain policy check (882 entries in 16s)
[ERR_PNPM_MISSING_TARBALL_INTEGRITY] 1 lockfile entries failed verification:
  y-codemirror.next@0.3.5 has no "integrity" field, so its downloaded tarball cannot be verified

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.
Progress: resolved 879, reused 0, downloaded 1, added 0

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.

0 participants