Skip to content

chore(deps): update dependency typescript-eslint to v8.59.4#487

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 22, 2026

This PR contains the following updates:

Package Change Age Confidence
typescript-eslint (source) 8.59.28.59.4 age confidence

Release Notes

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

v8.59.4

Compare Source

🩹 Fixes
  • typescript-eslint: export Compatible* types from typescript-eslint to resolve pnpm TS error (#​12340)
❤️ Thank You

See GitHub Releases for more information.

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

v8.59.3

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: (in timezone America/Chicago)

  • Branch creation
    • Only on Friday (* * * * 5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 requested a review from jdx as a code owner May 22, 2026 06:34
@renovate renovate Bot enabled auto-merge (squash) May 22, 2026 06:34
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 22, 2026

PR author is in the excluded authors list.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 22, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedtypescript-eslint@​8.59.2 ⏵ 8.59.4100 +110074 +198100

View full report

@renovate renovate Bot force-pushed the renovate/typescript-eslint-monorepo branch from a070e25 to 643a0b4 Compare May 25, 2026 18:13
@renovate renovate Bot changed the title chore(deps): update dependency typescript-eslint to v8.59.3 chore(deps): update dependency typescript-eslint to v8.59.4 May 25, 2026
@socket-security
Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.jsonnpm/typescript-eslint@8.59.4npm/@typescript-eslint/eslint-plugin@8.59.4

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.59.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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