fix(ci): publish release as draft to support immutable releases

[fengmk2]

Summary

The release workflow fails on the asset-upload step on repos with GitHub's immutable releases feature enabled. Failing run: https://github.com/voidzero-dev/vite-plus/actions/runs/25673521844/job/75370568926

Cannot upload asset vp-setup-x86_64-pc-windows-msvc.exe to an immutable release.
GitHub only allows asset uploads before a release is published, but draft
prereleases publish with the release.published event instead of release.prereleased.

softprops/action-gh-release creates prerelease: true, draft: false in a single API call, so the release is already published by the time assets upload. On immutable repos that's rejected.

Fix

• Create the release as a draft so assets attach while it's still mutable.
• Add a follow-up gh release edit ... --draft=false step to publish it.

The single release.published event still fires once, after assets are in place. GITHUB_TOKEN already has contents: write on the Release job, which is all gh release edit needs.

Test plan

• Trigger a manual Release workflow run with npm_tag: alpha and verify both the Create GitHub Release (draft) and Publish GitHub Release steps succeed
• Confirm assets (vp-setup-*.exe) appear on the published release
• Confirm the GitHub release transitions from draft to published prerelease

[netlify]

✅ Deploy Preview for viteplus-preview canceled.

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

[fengmk2]

ci test works https://github.com/voidzero-dev/vite-plus/actions/runs/25719780413/job/75521718866