Release Process

+This document describes how to release a new version of RustChat. + +## Versioning Strategy + +RustChat follows Semantic Versioning. +Both backend and frontend versions are kept in sync. + +## How to Release + +1. Bump the version:

• Run the helper script to update Cargo.toml and package.json:
• ./scripts/bump-version.sh <new_version>
• Example: ./scripts/bump-version.sh 0.1.0

+2. Update CHANGELOG.md:

• Ensure all notable changes since the last release are documented in CHANGELOG.md.

+3. Commit the changes:

• git add .
• git commit -m "chore: release v0.1.0"

+4. Tag the release:

• git tag v0.1.0

+5. Push to GitHub:

• git push origin main --tags

+## CI/CD Automation + +Upon pushing a tag starting with v (e.g., v0.1.0): +- The Docker Publish workflow will build and push the backend and frontend images to GHCR with the version tag. +- The Release workflow will automatically create a GitHub Release with an auto-generated changelog based on pull requests. +