Skip to content

v1.4.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 04:56
v1.4.4
2d0818f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Decepticon v1.4.4

This patch makes the startup update choice navigable with arrow keys and hardens startup recovery for existing installations.

Changes

  • Select Update now or Skip with arrow keys and confirm with Enter. Skip remains selected by default. (#966)
  • Recover an empty directory left at the opscontrol socket path by preserving it under a unique sibling backup name. Refuse to overwrite files, nonempty directories or symlinks. The daemon reports itself up only after binding the socket. The Compose socket bind refuses to create a missing host path. (#967)
  • Recover from specific Docker missing-network startup errors with bounded retries. Only empty networks belonging to the current project's configured nonexternal networks can be removed; active/foreign networks are refused. Preserve workspace/auth environment and profiles. No down, prune or volume deletion occurs. (#968)

Updating

decepticon update --channel latest
decepticon

Installed older launchers retain their old update prompt until upgraded. Arrow navigation applies after installing this patch. Existing database credentials, volumes and engagement data do not need to be recreated.

Verification

Actual prompt PTY checks covered default Enter/Skip, Up+Enter, Up+Down+Enter, cancellation and non-TTY. Real updated daemon and Docker checks covered directory inode/owner/mode preservation, refusal of arbitrary paths, missing bind-source rejection and recovered socket mounting.

Before final publication, the built v1.4.4 launcher and versioned images were directly tested on WSL2 in a separate installation. The normal launcher created an engagement with only its name, started all seven services, verified the agent stack, and opened the actual v1.4.4 interactive CLI. A real Codex OAuth turn using auth/gpt-6.1-sol returned the requested readiness marker; the persisted server state recorded 10,720 input tokens, 10 output tokens, no tool calls and normal completion. Candidate binary and configuration checksums were verified.

The reported existing local installation was repaired by recreating its two empty stale managed networks and preserving its socket directory. Its seven services passed startup checks and the actual CLI loaded its agent catalog. Automatic network recovery was separately exercised through the production Compose.Up entrypoint with an executable Docker fixture, plus real Docker CLI transport against an owned Engine API fixture. The new automatic helper was not tested by intentionally corrupting the user's live Docker daemon.

Full changelog: v1.4.3...v1.4.4

Assets 20
Loading