Skip to content

chore(deps): update typescript-eslint monorepo to v8.64.0#514

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-eslint-monorepo
Open

chore(deps): update typescript-eslint monorepo to v8.64.0#514
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-eslint-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@typescript-eslint/utils (source) 8.62.08.64.0 age confidence
typescript-eslint (source) 8.62.08.64.0 age confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/utils)

v8.64.0

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.63.0

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.62.1

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (typescript-eslint)

v8.64.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.63.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

v8.62.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.


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 these updates 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 requested a review from bzp2010 as a code owner July 4, 2026 12:02
@renovate renovate Bot changed the title chore(deps): update typescript-eslint monorepo to v8.62.1 chore(deps): update typescript-eslint monorepo to v8.63.0 Jul 6, 2026
@renovate renovate Bot force-pushed the renovate/typescript-eslint-monorepo branch from 131f06e to d7f0d26 Compare July 7, 2026 22:07
@renovate renovate Bot force-pushed the renovate/typescript-eslint-monorepo branch from d7f0d26 to 3854062 Compare July 13, 2026 04:34
@renovate renovate Bot changed the title chore(deps): update typescript-eslint monorepo to v8.63.0 chore(deps): update typescript-eslint monorepo to v8.64.0 Jul 13, 2026
@renovate

renovate Bot commented Jul 13, 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 8 workspace projects
? Verifying lockfile against supply-chain policies (749 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 29, reused 0, downloaded 0, added 0
Progress: resolved 43, reused 0, downloaded 0, added 0
Progress: resolved 45, reused 0, downloaded 0, added 0
Progress: resolved 48, reused 0, downloaded 0, added 0
Progress: resolved 49, reused 0, downloaded 0, added 0
Progress: resolved 51, reused 0, downloaded 0, added 0
Progress: resolved 53, reused 0, downloaded 0, added 0
Progress: resolved 54, reused 0, downloaded 0, added 0
Progress: resolved 58, reused 0, downloaded 0, added 0
[WARN] Request took 11191ms: https://registry.npmjs.org/typescript
Progress: resolved 59, reused 0, downloaded 0, added 0
Progress: resolved 67, reused 0, downloaded 0, added 0
Progress: resolved 166, reused 0, downloaded 0, added 0
Progress: resolved 362, reused 0, downloaded 0, added 0
Progress: resolved 372, reused 0, downloaded 0, added 0
Progress: resolved 379, reused 0, downloaded 0, added 0
✓ Lockfile passes supply-chain policies (749 entries in 19.5s)
Progress: resolved 383, reused 0, downloaded 0, added 0
Progress: resolved 384, reused 0, downloaded 0, added 0
Progress: resolved 386, reused 0, downloaded 0, added 0
Progress: resolved 404, reused 0, downloaded 0, added 0
Progress: resolved 620, reused 0, downloaded 0, added 0
Progress: resolved 628, reused 0, downloaded 0, added 0
Progress: resolved 697, reused 0, downloaded 0, added 0
Progress: resolved 719, reused 0, downloaded 0, added 0
Progress: resolved 759, reused 0, downloaded 2, added 0
[ERR_PNPM_STRICT_MIN_RELEASE_AGE_REQUIRES_SAVE] minimumReleaseAgeStrict cannot be combined with --no-save: approval would require writing to minimumReleaseAgeExclude in pnpm-workspace.yaml, which --no-save prevents.

Drop --no-save so the exclude list can be persisted, or set minimumReleaseAgeStrict: false to let the install proceed without prompting (the lockfile would still trigger the auto-collect on the next normal install).

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