Skip to content

πŸš€ Releases

Follow this checklist to cut a new Panoramax frontend release using semantic versioning.

Compatibility

Keep MAJOR.MINOR in sync with the other Panoramax components. Different PATCH versions are fine as long as the API/UI remain compatible.


πŸ“ Release Checklist

# 1. Start from develop
git switch develop

# 2. Update version number
vim package.json          # bump version

# 3. Regenerate documentation
npm run docs

# 4. Update changelog
vim CHANGELOG.md          # move "Unreleased" -> new version

# 5. Commit and tag
git add .
git commit -m "Release x.x.x"
git tag -a x.x.x -m "Release x.x.x"
git push origin develop

# 6. Merge into main
git switch main
git merge develop
git push origin main --tags

Tips

  • Use consistent version formatting everywhere (package.json, CHANGELOG).
  • Double-check docs output in dist/docs/ before pushing.