Release Process
How to release a new version of Vant.
Versioning
Vant uses Semantic Versioning:
MAJOR.MINOR.PATCH
v0.8.6
| Type | Example | When |
|---|---|---|
| PATCH | 1.2.3 -> 1.2.4 | Bug fixes |
| MINOR | 0.8.6 -> 0.9.0 | New features |
| MAJOR | 0.8.6 -> 1.0.0 | Breaking changes |
Release Checklist
Steps for a successful release.
1. Pre-Release
- All tests pass
- No lint errors
- Update CHANGELOG.md
- Update version in lib/version.js
2. Release
Bump version and tag:
# Bump version
vant bump # patch
vant bump minor # minor
vant bump major # major
# Tag and push
git push origin main --tags
3. Post-Release
- Verify CI passes
- Update GitHub release notes
- Announce (if applicable)
Bump Command
Use the bump command to increment versions:
# Patch release (example: 1.2.3 → 1.2.4)
vant bump
# Minor release (0.8.6 → 0.9.0)
vant bump minor
# Major release (0.8.6 → 1.0.0)
vant bump major
Git Tags
Tags are created automatically:
# List tags
git tag -l
# Push tags
git push origin main --tags
GitHub Releases
After pushing tags:
- Go to Releases
- Click “Draft a new release”
- Select the tag
- Add release notes
- Publish
Docker Tags
Deploy Vant in a container for consistent environments.
# Build and push (example: v0.9.0)
docker build -t dhaupin/vant:v0.9.0 .
docker push dhaupin/vant:v0.9.0
# Latest tag
docker tag dhaupin/vant:v0.9.0 dhaupin/vant:latest
docker push dhaupin/vant:latest
Related
- CLI Reference - All commands
- Docker - Container build