Release & Versioning

Purpose: Define how we cut releases and track changes. Audience: Owner, Developer Prerequisites: CI/CD access.

Versioning

• Semantic versioning (MAJOR.MINOR.PATCH)
• Docs-only updates can bump PATCH.

Release flow

• Create release branch release/x.y.z.
• Update docs/changelog.md.
• Tag: git tag vX.Y.Z && git push --tags.
• Deploy to staging; verify smoke tests.
• Promote to production.

Changelog

• Keep concise, action-oriented entries per release.
• Include db migrations, functions, and env changes.

Next steps

• See docs/operations/deployment.md for deployment details.