chore(deps): update vite-plus to v1.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vite (source)	1.2.0 → 1.3.0
vite-plus (source)	1.2.0 → 1.3.0

---

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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
	@​voidzero-dev/​vite-plus-core@​1.2.0 ⏵ 1.3.0	+1		+1	+2
	vite-plus@​1.2.0 ⏵ 1.3.0				+2

View full report

[fengmk2]

@copilot fix ci fail

[Copilot]

@copilot fix ci fail

CI failed in vp install: the lockfile now pins vitest/@vitest/* 5.0.5, which vite-plus 1.3.0 requires and which was published inside the minimumReleaseAge window. I added vitest and @vitest/* to minimumReleaseAgeExclude in pnpm-workspace.yaml. I couldn't run CI from here, so it still needs a re-run to confirm the fix.

[fengmk2]

@copilot fix ci fail

[Copilot]

@copilot fix ci fail

The only remaining failure was the build job's "Verify dist is up to date" step, because the committed bundles were stale for 1.3.0. The publish-bundle workflow was awaiting approval, so I rebuilt dist/ locally with pnpm build and pushed it in 0109569. CI still needs a re-run to confirm.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.