CI/CD

Use this reference before changing GitHub Actions or release automation.

Prefer the documented Vite+ setup:

- uses: voidzero-dev/setup-vp@v1
  with:
    node-version-file: ".node-version"
    cache: true
- run: vp install
- run: vp check
- run: vp test
- run: vp build

Action Inputs

voidzero-dev/setup-vp@v1 exposes:

Defaults

• Prefer voidzero-dev/setup-vp@v1 over hand-rolled Node/Corepack bootstrapping unless the repo has a proven exception.
• Prefer setup-vp's built-in Node and package-manager bootstrap over adding separate CI-time vp env setup steps unless the repo has a specific environment need the action does not cover.
• Prefer vp install over separate package-manager bootstrap logic when Vite+ is the tool owner. The action's run-install: true input collapses setup + install into one step.
• Prefer vp config when the repo wants stock hooks or agent integration instead of hand-rolled hook setup.
• Prefer one repo-local verify entrypoint if CI needs extra repo-specific commands.
• Keep release orchestration in GitHub Actions when the repo has npm, GitHub Release, binary, or Homebrew automation that goes beyond stock Vite+.
• Vite+ can run repo scripts, but it does not make runtime-installed release plugins reproducible by itself. For semantic-release jobs, follow gh-release-pipeline: keep CI/CD-only plugins in the workflow's extra_plugins input with exact versions instead of adding release-only packages to repo devDependencies.
• When CI behavior must stay aligned with a repo's chosen Vite+ release, pin the setup-vp action's version input explicitly. Treat the local vite-plus dependency version in package.json as separate from the action's runtime version.

Guardrails

• Prefer vp run <script> (or vpr <script>) when CI needs a repo-specific script that Vite+ does not replace.
• Preserve release-only steps while making the surrounding workflow more stock.
• Keep packaging and publish steps that Vite+ does not own.