chore(deps): update oxlint monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
oxc-minify (source)	^0.105.0 → ^0.106.0
oxfmt (source)	^0.20.0 → ^0.21.0
oxlint (source)	1.32.0 → 1.36.0

---

Release Notes

oxc-project/oxc (oxc-minify)

v0.106.0

🚀 Features

• e031056 codegen: Add sourcemap feature flag (#​17305) (Boshen)
• 8e4409a minifier: Add invalid_import_side_effects option (#​17300) (sapphi-red)

oxc-project/oxc (oxfmt)

v0.21.0

Compare Source

🐛 Bug Fixes

• 0a39cba oxfmt: Update wrong doc comment (#​17288) (leaysgur)

oxc-project/oxc (oxlint)

v1.36.0

Compare Source

v1.35.0

Compare Source

🚀 Features

• 9e624c9 linter/react: Add version to ReactPluginSettings (#​17169) (camc314)

v1.34.0

Compare Source

🚀 Features

• a0f74a0 linter/config: Allow aliasing plugin names to allow names the same as builtin plugins (#​15569) (Cameron)

🐛 Bug Fixes

• 005ec25 linter: Permit $schema .oxlintrc.json struct (#​17060) (Copilot)
• d446c43 linter: Prevent extra fields from being present on oxlint config file (#​16874) (connorshea)

v1.33.0

Compare Source

---

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

[renovate]

⚠️ 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 73 workspace projects
.                                        |  WARN  There are cyclic workspace dependencies: /tmp/renovate/repos/github/eggjs/egg/packages/cluster, /tmp/renovate/repos/github/eggjs/egg/plugins/mock, /tmp/renovate/repos/github/eggjs/egg/packages/egg; /tmp/renovate/repos/github/eggjs/egg/tegg/core/runtime, /tmp/renovate/repos/github/eggjs/egg/tegg/core/test-util
 ERROR  Invalid Version: ^1.32.0

pnpm: Invalid Version: ^1.32.0
    at new _SemVer (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:38216:17)
    at compare (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:38609:65)
    at Object.eq (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:38693:31)
    at installSome (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:158868:223)
    at _install (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:158810:21)
    at async mutateModules (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:158670:23)
    at async recursive (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:160054:100)
    at async recursiveInstallThenUpdateWorkspaceState (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:160565:31)
    at async installDeps (/opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:160372:11)
    at async /opt/containerbase/tools/pnpm/10.26.2/24.12.0/node_modules/pnpm/dist/pnpm.cjs:193815:23

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	keygrip@​1.1.0
	@​types/​encodeurl@​1.0.3
	@​types/​koa-range@​0.3.5
	@​types/​lodash.snakecase@​4.1.9
	@​types/​sqlstring@​2.3.2
	@​types/​destroy@​1.0.3
	husky@​9.1.7
	@​types/​fresh@​0.5.3
	@​types/​fs-readdir-recursive@​1.1.3
	@​types/​vary@​1.1.3
	@​types/​parseurl@​1.3.3
	@​types/​on-finished@​2.3.5
	@​types/​stack-trace@​0.0.33
	@​types/​mime-types@​3.0.1
	@​types/​type-is@​1.6.7
	@​vitest/​coverage-v8@​4.0.15
	@​types/​js-beautify@​1.14.3
	@​types/​body-parser@​1.19.6
	@​types/​express@​5.0.3
	@​types/​js-yaml@​4.0.9
	@​typescript/​native-preview@​7.0.0-dev.20251223.1
	@​types/​nunjucks@​3.2.6
	@​types/​escape-html@​1.0.4
	assert-file@​1.0.0
	@​types/​content-type@​1.1.9
	@​types/​common-tags@​1.8.4
	egg-plugin-puml@​2.4.0
	@​eggjs/​compressible@​3.0.0
	@​types/​extend@​3.0.4
	esbuild@​0.27.0
	@​types/​safe-timers@​1.1.2
	@​types/​urijs@​1.19.25
	@​types/​mustache@​4.2.6
See 85 more rows in the dashboard

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 entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/cheerio@1.1.2 → npm/entities@4.5.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/entities@4.5.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 entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/cheerio@1.1.2 → npm/entities@4.5.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/entities@4.5.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 entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/cheerio@1.1.2 → npm/entities@6.0.1 ℹ 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/entities@6.0.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		Obfuscated code: npm js-beautify is 100.0% likely obfuscated Confidence: 1.00 Location: Package overview From: pnpm-lock.yaml → npm/js-beautify@1.15.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/js-beautify@1.15.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

[cloudflare-workers-and-pages]

Deploying egg with    Cloudflare Pages

Latest commit:	8a3e305
Status:	🚫  Build failed.

View logs

[cloudflare-workers-and-pages]

Deploying egg-v3 with    Cloudflare Pages

Latest commit:	8a3e305
Status:	🚫  Build failed.

View logs