1 Dev Versioning
Forgejo Actions edited this page 2026-09-25 16:38:07 +00:00

Versioning

Memories uses pipeline-computed versioning. No manual version bumps.

See the automated version computation section in docs/dev/agent-workflow.md (under ## Versioning) for the operational workflow.

Policy Summary

Component Mechanism
MAJOR.MINOR Human-controlled git tag on main (e.g., v0.61)
PATCH Auto-computed commit count since the tag
Who bumps CI pipeline only. Agents never manually set version.
Env var MEMORIES_APP_VERSION injected by CI at build/deploy
Source placeholders package.json → 0.0.0, application.yml → ${MEMORIES_APP_VERSION:dev}

Reference

  • Spec: specs/015-automated-versioning/ — full design, acceptance criteria, migration steps
  • Implementation: scripts/ci/compute-version.sh
  • CI workflow: .forgejo/workflows/build-deploy.yml — version job step
  • Frontend: Vite define injects import.meta.env.VITE_APP_VERSION at build time
  • API: application.yml reads MEMORIES_APP_VERSION env var with dev fallback

Tagging a Release

git checkout main && git pull
git tag -a v0.62 -m "v0.62"
git push origin v0.62

Next push to main produces version 0.62.{n} where {n} = commits since tag.

Local Dev

Without a git tag: shows dev in UI, 0.0.{commit_count} in image tags. Set MEMORIES_APP_VERSION=dev in deploy/.env for explicit local version.