sanctum/GEMINI.md
MiTHRAL 90797d6dd9
All checks were successful
Build and Release Sanctum / Build App (push) Successful in 1m50s
chore: bump version to 1.0.3 and clarify tagging mandate
2026-04-24 15:36:44 -04:00

12 lines
840 B
Markdown

# Agent Mandates
## Versioning and Release Workflow
Before every `git push` that includes code changes, you MUST perform the following steps:
1. **Bump Version:** Increment the version in `package.json` (both `version` and `aviaVersion`).
2. **Update Branding:** If a version string is hardcoded in UI plugins (like `avia_core/headliner.js`), update it to match the new version.
3. **Migration Logic:** Update any migration logic in plugins to ensure users on the previous version are automatically updated to the new default.
4. **Tagging:** Create the git tag corresponding to the new version with a 'v' prefix (e.g., `git tag v1.0.x`).
5. **Push:** Push both the branch and the tags to the remote repository (`git push origin main --tags`).
This ensures the internal app state matches the release tag and prevents auto-updater loops.