chore(deps): update oxc apps

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
oxfmt (source)	0.55.0 → 0.56.0
oxlint (source)	1.70.0 → 1.71.0

---

Release Notes

oxc-project/oxc (oxfmt)

v0.56.0

Compare Source

oxc-project/oxc (oxlint)

v1.71.0

Compare Source

🚀 Features

• 0dc2405 linter: Add schema for eslint/no-restricted-properties (#​23619) (Sysix)
• b638d0e linter: Add schema for node/callback-return (#​23615) (Sysix)
• eb8bedc linter: Add schema for import/extensions (#​23557) (WaterWhisperer)
• 46f3625 linter: Implement node/no-sync rule (#​23589) (fujitani sora)
• b01739a linter: Add schema for unicorn/numeric-separators-style (#​23554) (Mikhail Baev)
• 68afd2a linter/node: Implement no-mixed-requires rule (#​23539) (fujitani sora)
• a421215 linter: Add schema for eslint/prefer-destructuring (#​23410) (WaterWhisperer)
• 84438be linter/jsdoc: Added missing options to require-param-description (#​23416) (kapobajza)
• 51910df linter/jsdoc: Add missing options to require-param-type rule (#​23418) (kapobajza)
• e90925f linter/unicorn: Implement prefer-number-coercion rule (#​23497) (Shekhu☺️)
• dd1c866 linter/vue: Implement no-async-in-computed-properties rule (#​23493) (bab)
• b02444e linter: Add schema for react/jsx-no-script-url (#​23475) (WaterWhisperer)
• a8dce46 linter/unicorn: Implement max-nested-calls rule (#​23461) (arieleli01212)

🐛 Bug Fixes

• a303c23 linter/jsx-a11y: Align anchor-is-valid config with upstream (#​23446) (camc314)

📚 Documentation

• b50bf4d linter: Remove manually written options doc for eslint/arrow-body-style (#​23490) (Mikhail Baev)

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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/​oxfmt@​0.55.0 ⏵ 0.56.0	-16
	npm/​oxlint@​1.70.0 ⏵ 1.71.0	+1		+1	+1

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		Obfuscated code: npm oxfmt is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: napi/angular-compiler/e2e/compare/package.json → npm/oxfmt@0.56.0 ℹ 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/oxfmt@0.56.0. 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		Obfuscated code: npm oxfmt is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: napi/angular-compiler/e2e/compare/package.json → npm/oxfmt@0.56.0 ℹ 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/oxfmt@0.56.0. 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