octopusreview/octopus v1.2.17 on GitHub

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.2.17.

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.2.17
docker compose -f docker-compose.selfhost.yml pull

Follow 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 version

The in-app Updates page (Settings → System → Updates) shows when a new
release is available, along with this upgrade snippet.

What's Changed

fix(web): record verified repository index completion by @cemoso in #934
fix(analytics): record first successful repository index (#924) by @onurv-ui in #932
fix(web): isolate index generations during rolling upgrades by @cemoso in #935
chore: prepare 1.2.17 release metadata by @cemoso in #936

New Contributors

@onurv-ui made their first contribution in #932

Full Changelog: v1.2.16...v1.2.17