1 Upgrades And Versioning
Forgejo Actions edited this page 2026-09-25 17:00:22 +00:00

Upgrades and Versioning

Versions are computed by the pipeline, not bumped by hand. MAJOR.MINOR comes from a human-controlled git tag on main, and PATCH is the commit count since that tag. CI then injects MEMORIES_APP_VERSION into the API and image tags.

Builds and deployments run through Forgejo Actions and only on main. Scoped detection rebuilds only the services whose files changed; branch pushes run scoped tests, while nightly or manual runs exercise the full suite. The correct upgrade path is therefore to merge to main through CI, not to run manual docker operations.

Flyway migrations run automatically when the API starts. Two cautions:

  • Heavy migrations, such as a large HNSW index build that can take around four to five minutes, have outlasted the 300-second deploy wait (ISSUE-065).
  • Swapping to the PostGIS image for an existing volume requires a database backup first, and at least one migration fails on affected installs (ISSUE-022).

See Versioning for how versions are derived and Forgejo Deployment Pipeline for the pipeline itself. Known Issues and Operator Diagnostics tracks the migration caveats.

Details