RC images use the base application version and do not move latest aliases.
Stable images promote accepted RC digests without rebuilding.
Octopus Cloud can now connect to private LAN/VPN Forgejo through a local
connector. Choose your setup at https://octopus-review.ai/docs/integrations#forgejo.
The standalone connector image is
ghcr.io/octopusreview/octopus-selfhost:forgejo-connector-1.3.0-rc.1.
Before upgrading, read this version's Upgrade notes.
They specify the order for updating services and applying migrations.
Schema prerequisites may need migrations first; a new model catalog
entry may need compatible web and review workers running first.
Prepare the self-hosted upgrade:
git fetch --tags && git checkout vX.Y.Z # for the compose file + migrations
export OCTOPUS_VERSION=1.3.0-rc.1
docker compose -f docker-compose.selfhost.yml pullFollow the Upgrade notes before running docker compose -f docker-compose.selfhost.yml up -d
and bunx prisma migrate deploy from packages/db with your configured
DATABASE_URL. The runtime image ships no migrations; use the tag checkout.
Then verify:
curl -fsS http://localhost:43300/api/health # expect {"status":"ok"}
curl -fsS http://localhost:43300/api/version # confirm the new versionThe in-app Updates page (Settings → System → Updates) shows when a new
release is available, along with this upgrade snippet.
What's Changed
- feat(analytics): record review attempt outcomes (#924) by @onurv-ui in #940
- feat(analytics): expose first index timestamp in repository view (#924) by @onurv-ui in #939
- fix(web): preserve superseded outcomes for stale large reviews by @cemoso in #941
- feat(analytics): record organisation and account creation provenance (#924) by @onurv-ui in #938
- chore(release): prepare 1.3.0 analytics milestones by @cemoso in #942
Full Changelog: v1.2.17...v1.3.0-rc.1