chore: update void to 0.10.8 and switch main deploy to OIDC#39
Conversation
- Bump void 0.9.3 to 0.10.8 - Connect repo to Void project vp-setup via the github_actions executor (OIDC) - Add .github/workflows/void-deploy.yml using GitHub OIDC, no VOID_TOKEN secret - Remove the old token-based deploy.yml so main does not double-deploy
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
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.
|
|
✅ Staging deployment successful! Preview: https://vp-setup-staging.void.app/ |
What
void0.9.3to0.10.8(catalog + lockfile).main) from a storedVOID_TOKENsecret to GitHub OIDC.Details
Connected
voidzero-dev/setup.viteplus.dev(main) to Void projectvp-setupwith thegithub_actionsbuild executor viavoid github connect. The authorized deploy workflow is.github/workflows/void-deploy.yml.The new workflow uses
permissions: id-token: write, sovoid deploymints a short-lived GitHub OIDC token and exchanges it for a project-scoped deploy token at deploy time. There is no long-livedVOID_TOKENto store or rotate. It follows this repo's toolchain (taiki-e/checkout-action+voidzero-dev/setup-vp+vpx void deploy).The old token-based
deploy.ymlis removed somaindoes not double-deploy.Notes
ci.yml's separate staging deploy (vp-setup-staging, on PRs) still usesVOID_TOKENand is left unchanged.vp checkandvp buildpass on the new version.