Release
Use the local Changesets workflow only.
Preconditions
- Confirm
npm whoamisucceeds. - Confirm release-worthy code changes are already committed.
- Confirm a changeset exists for each package that should publish.
- Confirm the root Vite+ task graph still defines the release validation flow.
- Run the root validation tasks and fix failures before versioning or publishing.
- Confirm the worktree is clean before versioning unless the user explicitly wants to review pending changes first.
Workflow
- Review pending changesets and the packages they affect.
- Add or fix
.changeset/*.mdfiles if needed. - Run
pnpm exec vp run build. - Run
pnpm exec vp run check. - Run
pnpm exec vp run test. - Run
pnpm exec changeset version. - Review generated version and changelog updates.
- Commit the release versioning changes.
- Run
pnpm exec vp run release. - Push the release commit and tags.
- Verify the published package versions with
npm view.
Rules
- Prefer
patchfor pre-1.0 packages unless the user explicitly asks for a different bump. - Keep the release flow local. Do not instruct the user to wait for CI, merge a version PR, or use a GitHub release bot.
- Do not assume root
package.jsonscripts exist when the repo models workflow through Vite+ tasks. Check the rootvite.config.tstask graph first. - If publish fails because of auth, OTP, or npm state, fix that first and rerun
pnpm exec vp run release. - If push is rejected, rebase on
mainand push again with tags.