840 B
840 B
Agent Mandates
Versioning and Release Workflow
Before every git push that includes code changes, you MUST perform the following steps:
- Bump Version: Increment the version in
package.json(bothversionandaviaVersion). - Update Branding: If a version string is hardcoded in UI plugins (like
avia_core/headliner.js), update it to match the new version. - Migration Logic: Update any migration logic in plugins to ensure users on the previous version are automatically updated to the new default.
- Tagging: Create or move the git tag corresponding to the new version (e.g.,
git tag -f 1.0.x). - Push: Push both the branch and the tags to the remote repository (
git push origin main --force --tags).
This ensures the internal app state matches the release tag and prevents auto-updater loops.