Octopus 1.2.4 makes repository setup clearer from connecting a provider to receiving the first review. PR #871.
- The dashboard follows one repository through connection, readiness, opening a PR and its first successfully published review. It prefers a connected repository and shows automatic indexing and analysis as preparation progress. Manual indexing is optional.
- Auto Review shows its saved setting and can be changed during preparation. Indexing and one-off reviews no longer turn a disabled setting back on.
- Integration cards separate authorized access, repository sync and webhook configuration. Retry and repair guidance covers GitHub, Bitbucket, GitLab and Forgejo while preserving webhook ownership and signing secrets.
- Indexing, cancellation and sync errors stay visible, with recovery links for the correct provider. Retrying indexing starts a fresh log view.
Take a database backup, then apply both additive migrations before starting updated services:
20260921160000_integration_setup_status: existing connections initially show unchecked setup until their next sync or setup check; authorization is retained.20260921170000_first_review_completion: records newly confirmed review publication. Historical reports are not backfilled, and later failed reruns do not erase an earlier confirmed completion.
For deployments with separate services, update the review engine before the web application, after migrations. The standard self-hosted Compose deployment runs review workers inside web and updates them together.
Self-hosted upgrades use the existing documented checkout-and-pull method. The runtime image does not contain migrations. These commands use the standard Compose database and ports; retain your configured values if customized.
git fetch --tags && git checkout v1.2.4
export OCTOPUS_VERSION=1.2.4
docker compose -f docker-compose.selfhost.yml pull
# Apply migrations while the previous version is still running.
cd packages/db
DATABASE_URL=postgresql://octopus:octopus@localhost:43332/octopus bunx prisma migrate deploy
cd ../..
# Start the updated application and its bundled review workers.
docker compose -f docker-compose.selfhost.yml up -d
curl -fsS http://localhost:43300/api/health
curl -fsS http://localhost:43300/api/versionConfirm health is ok and the version is 1.2.4. Refresh indexed help content after deployment through the existing administrator POST /api/admin/seed-docs process.
Forgejo setup remains separated into Cloud + public HTTPS, Cloud + private LAN/VPN connector, and self-hosted Octopus + direct access. Forgejo repository webhooks still require manual configuration.
Validation: 1,870 automated tests passed, 55 skipped, 0 failed; 13 browser checks passed; Octopus review scored 4/5. A live provider-to-publication test remains unverified; these checks used controlled fixtures and do not establish live webhook delivery.