Delete a job safely
otter delete is irreversible, so it prints what it will destroy and waits for confirmation. A path is refused, and a job with a run in flight is refused rather than half-removed.
v0.5.3 · 2026-10-08
Otter/Changelog
Changelog
Otter publishes release notes with every tag, and this is the readable version of that history. In-progress work lives on the repository; nothing here is a roadmap promise.
otter delete is irreversible, so it prints what it will destroy and waits for confirmation. A path is refused, and a job with a run in flight is refused rather than half-removed.
v0.5.3 · 2026-10-08
otter deploy --cloud now promotes an existing release instead of building a new one, so what reaches production is byte-for-byte what you tested. --build restores the old packaging behaviour, and jobs can now be deleted.
v0.5.2 · 2026-10-07
Four interfaces cross the runtime's boundary — manifest schema, Python SDK, CLI JSON and the HTTP API — and all four stopped moving. A compatibility and deprecation policy now says what counts as a change and how one is retired.
v0.4.0 · 2026-10-03
History
2026-10-08
v0.5.3
The client half of job deletion: otter delete --cloud <name|id> behind a confirmation that names what it will destroy and waits for y. A scripted delete needs --yes — the prompt never reads a piped answer as consent. The argument is a job name or id, never a directory, and a job with a run in flight is refused with the run named.
2026-10-07
v0.5.2
Cloud deploys promote an existing release rather than packaging a new one, so the artifact you validated is the artifact that runs. Jobs can be deleted, including ones that only exist as a release.
2026-10-07
v0.5.1
A .deb per Linux architecture, so an install is apt install ./otter_*.deb rather than two binaries placed by hand. Homebrew's formula path is deprecated, so Linux ships a package and macOS keeps the cask.
2026-10-07
v0.5.0
otter login, otter deploy --cloud, org-bound credentials, and one-container pooled tenants split across two uids. The first release where a stranger can put a job on managed compute without talking to us.
2026-10-03
v0.4.0
A scoped control credential, first-class dynamic schedules, pinned job configuration, a reachable-but-scoped remote API, and the published compatibility policy. After this, building on Otter stops being a moving target.
2026-10-02
v0.3.0
Upgrades can be watched, queue age and freshness appear on /health, retention is automatic, and the operating procedures ship as drills someone else can actually run.
2026-09-28
v0.2.0
Recovery is complete rather than best-effort, startup can refuse to serve with stranded work, Linux children die with the daemon, and the runtime contract is published.
2026-09-28
v0.1.19
Complete recovery reads, claimed runs are re-enqueued rather than abandoned, and leaked capacity is released. Commit subjects only — this one predates curated release notes.
Reading the version numbers. Within a major release, a patch is bug fixes only and a minor is additive; removing or changing the meaning of anything in a frozen interface requires a major. The runtime contract is versioned separately and increments when a promise — or a non-promise — changes.