Update dependency @eslint/config-helpers to v0.5.2 - autoclosed

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/config-helpers (source)	0.4.2 → 0.5.2

---

Release Notes

eslint/rewrite (@​eslint/config-helpers)

v0.5.2

Compare Source

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^1.0.1 to ^1.1.0

v0.5.1

Compare Source

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^1.0.0 to ^1.0.1

v0.5.0

Compare Source

⚠ BREAKING CHANGES

• Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#​297)

Features

• Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#​297) (acc623c)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^0.17.0 to ^1.0.0

---

Configuration

📅 Schedule: 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.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​grunt-jscs@​3.0.1
	npm/​btoa@​1.2.1
	npm/​karma-detect-browsers@​2.3.3
	npm/​grunt-contrib-copy@​1.0.0
	npm/​karma-browserstack-launcher@​1.6.0
	npm/​load-grunt-tasks@​5.1.0
	npm/​grunt-exec@​3.0.0
	npm/​grunt-postcss@​0.9.0
	npm/​ip@​2.0.1
	npm/​grunt@​1.6.1
	npm/​cross-env@​7.0.3
	npm/​grunt-html@​17.0.1
	npm/​karma-firefox-launcher@​2.1.3
	npm/​karma-chrome-launcher@​3.2.0
	npm/​karma-qunit@​4.2.1
	npm/​karma@​6.4.4
	npm/​grunt-contrib-clean@​2.0.1
	npm/​grunt-contrib-concat@​2.1.0
	npm/​grunt-contrib-less@​3.0.0
	npm/​grunt-contrib-jshint@​3.2.0
	npm/​grunt-contrib-cssmin@​5.0.0
	npm/​grunt-contrib-uglify@​5.2.2
	npm/​grunt-stylelint@​0.10.1
	npm/​autoprefixer@​9.8.8

View full report

[socket-security]

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		Critical CVE: Prototype Pollution in npm lodash CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: xwiki-platform-core/xwiki-platform-bootstrap/src/main/package-lock.json → npm/grunt-jscs@3.0.1 → npm/lodash@3.10.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash@3.10.1. 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.
Warn		Critical CVE: Prototype Pollution in npm lodash CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: xwiki-platform-core/xwiki-platform-bootstrap/src/main/package-lock.json → npm/grunt-jscs@3.0.1 → npm/lodash@4.6.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash@4.6.1. 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