feat(deps): upgrade upstream dependencies

[voidzero-guard]

Summary

• Automated upgrade of upstream dependencies.
• Bumps rolldown to v1.1.2 and the oxc npm packages from 0.136.0 to 0.137.0.
• Requires code adjustments: an oxc parser API rename in vite_static_config, dropping the native wasm fallback plugin in the Vite brand patch, and Cargo dependency cleanup alongside the oxc Rust crate bumps.
• build-upstream failed; see Build status.

Dependency updates

Package	From	To
rolldown	d7f919c	v1.1.2 (e0d0b1b)
@oxc-project/runtime	0.136.0	0.137.0
@oxc-project/types	0.136.0	0.137.0
oxc-minify	0.136.0	0.137.0
oxc-parser	0.136.0	0.137.0
oxc-transform	0.136.0	0.137.0

Unchanged dependencies

• vite: v8.0.16 (f94df87)
• vitest: 4.1.9
• @vitest/browser: 4.1.9
• @vitest/browser-playwright: 4.1.9
• @vitest/browser-preview: 4.1.9
• @vitest/browser-webdriverio: 4.1.9
• @vitest/expect: 4.1.9
• @vitest/mocker: 4.1.9
• @vitest/pretty-format: 4.1.9
• @vitest/runner: 4.1.9
• @vitest/snapshot: 4.1.9
• @vitest/spy: 4.1.9
• @vitest/utils: 4.1.9
• tsdown: 0.22.3
• @oxc-node/cli: 0.1.0
• @oxc-node/core: 0.1.0
• oxfmt: 0.55.0
• oxlint: 1.70.0
• oxlint-tsgolint: 0.23.0
• @vitejs/devtools: 0.3.3

Code changes

• crates/vite_static_config/src/lib.rs: rename oxc parser result field errors -> diagnostics to match the oxc 0.137 API.
• packages/tools/src/brand-vite.ts: drop the native viteWasmFallbackPlugin (removed upstream in rolldown #9775); the JS wasmHelperPlugin still handles wasm imports.
• Cargo.toml: bump oxc 0.135.0 -> 0.137.0, oxc_resolver 11.21.0 -> 11.21.3, oxc_sourcemap 7 -> 8.0.1; cargo shear cleanup removes unused deps (commondir, num-format, ropey, urlencoding, rolldown_plugin_vite_wasm_fallback) and adds idna_adapter, supports-color.
• packages/cli/binding/index.cjs, packages/cli/binding/index.d.cts: regenerated NAPI bindings (adds BindingErrorStage export).
• pnpm-workspace.yaml: catalog version bumps and minimumReleaseAgeExclude additions.

Build status

• sync-remote-and-build: success
• build-upstream: failure

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

Name	Link
🔨 Latest commit	1f48500
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a38debe70e56400088a2349

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​tokio@​1.50.0 ⏵ 1.52.3	-1
	cargo/​nix@​0.31.2 ⏵ 0.31.3
	npm/​@​babel/​preset-typescript@​7.29.7
	npm/​@​oxc-project/​runtime@​0.137.0
	cargo/​reqwest@​0.13.2 ⏵ 0.13.4	+2
	cargo/​rustls@​0.23.37 ⏵ 0.23.40
	cargo/​napi@​3.9.0 ⏵ 3.9.3
	cargo/​serde_json@​1.0.149 ⏵ 1.0.150
	npm/​oxc-parser@​0.137.0
	cargo/​chrono@​0.4.44 ⏵ 0.4.45
	cargo/​clap@​4.6.0 ⏵ 4.6.1
	cargo/​clap_complete@​4.6.0 ⏵ 4.6.5	+1
	cargo/​ignore@​0.4.25 ⏵ 0.4.26
	cargo/​indexmap@​2.13.0 ⏵ 2.14.0
	cargo/​oxc_allocator@​0.135.0 ⏵ 0.137.0
	cargo/​oxc_ast@​0.135.0 ⏵ 0.137.0
	cargo/​oxc_parser@​0.135.0 ⏵ 0.137.0
	cargo/​oxc_resolver@​11.21.0 ⏵ 11.21.3
	cargo/​oxc_span@​0.135.0 ⏵ 0.137.0
	cargo/​rayon@​1.11.0 ⏵ 1.12.0
	cargo/​regex@​1.12.3 ⏵ 1.12.4
	cargo/​rustc-hash@​2.1.1 ⏵ 2.1.2
	cargo/​semver@​1.0.27 ⏵ 1.0.28
	cargo/​serial_test@​3.4.0 ⏵ 3.5.0
	cargo/​tar@​0.4.45 ⏵ 0.4.46		+2
	cargo/​test-log@​0.2.19 ⏵ 0.2.21
	cargo/​which@​8.0.2 ⏵ 8.0.4
	npm/​oxc-transform@​0.137.0

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: cargo openssl is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/reqwest@0.13.4 → cargo/openssl@0.10.81 ℹ 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 cargo/openssl@0.10.81. 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: cargo tokio is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: bench/Cargo.toml → cargo/tokio@1.52.3 ℹ 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 cargo/tokio@1.52.3. 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: cargo zerocopy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/brush-parser@0.4.0 → cargo/criterion@0.7.0 → cargo/brush-parser@0.3.0 → cargo/zerocopy@0.8.52 ℹ 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 cargo/zerocopy@0.8.52. 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

[fengmk2]

Wait to update together after vite@8.1.0 is released