Repository navigation
v0.1.0-beta.12
Pre-release
Pre-release
·
563 commits
to main
since this release
- Per-deployment detail page. Every deployment row opens its own page: a queued → started → finished
timeline with queue wait and run time, who or what triggered it, the deployed commit (linked to the
repository), image tag and digest, the configuration diff against the previous deployment, the full build
log (following live while the deploy runs), and cancel / roll back / analyze actions — with honest notes
when a deploy was interrupted, recovered, auto-rolled-back or cancelled. The deployments list no longer
carries every build log, so the app page polls far less data. - PostgreSQL point-in-time recovery. Enable PITR per database: WAL archiving is turned on with a verified
restart, segments are shipped to the database's backup destination, physical base backups run on demand or
on a schedule, and the panel shows the recoverable window with a picker to restore to any second into a new
database. Retention is WAL-aware so a restorable base is never left without its WAL. - Restore-verify drills. Prove a backup restores: on demand or on a schedule, the latest backup is
restored into a disposable database and the result is recorded on the source; a watchdog alerts when the
drill stops running or starts failing. - Fleet rollouts. Deploy a release across many apps as canary → waves with a per-app health gate, a bake
window, fail-fast halt, resume, and a one-click fleet rollback to each app's previous version, with
notifications for halted / completed / rolled-back rollouts. - Post-cutover auto-rollback (opt-in per app). Rolling deploys can keep the previous container through a
soak window after traffic switches and revert automatically if the new version fails its health checks early. - Build secrets. Dockerfile builds can mount secrets via BuildKit
--secretso tokens never land in the
image or its history (unlike build args). - Secrets key rotation. Rotate
SECRETS_ENCRYPTION_KEYwithout re-entering any secret or touching your
apps (the hub restarts twice): keep the old key as a previous key, re-encrypt every stored secret from
Settings → Instance, then drop the old key once the panel says it is safe. - Digest-pinned updates. The signed release manifest now records each image's digest; the self-updater
pulls hub and web by digest and refuses an image whose version label does not match the release. Older
manifests keep updating by tag. - Safer installer and updater. A mandatory pre-update restore point (database dump +
.envcopy) before
any update;X-Forwarded-Foris trusted only from private, loopback or explicitly listed proxy peers; an
existing install turning HTTPS moves its raw ports to loopback (--keep-raw-portsopts out); atomic.env
writes; the updater also refreshes the bundled agent;bootstrap.shfetches by branch, tag or commit and
leaves a checkout thatgit pullcan update; abort paths restore the pre-run.env. - Deploys survive a hub restart. A deploy that is running when the hub restarts (or when the agent's
connection drops) is no longer marked failed blind. The agent keeps running it and keeps a local command
journal; when it reconnects the hub picks the deploy back up and records the real outcome — success,
failure, auto-rollback or cancelled — with the live log continuing in the panel. Only when the result
genuinely cannot be known (the agent itself restarted, or it never reports back before the deadline) does
the deploy show as interrupted, and the app's status is never changed on a guess. Requires the updated
agent (older agents keep the previous behaviour until they are updated via Update agent).