v1.4.0: AutoFix missions and governed integrations
Three features: the AutoFix mission type, governed outbound integrations, and the Assignment to Supply rename.
Full notes: 1.4.0 on GitHub.
AutoFix
A mission type that runs when a job fails. If an AutoFix mission is configured it is dispatched instead of AutoDiagnose, which is suppressed as redundant; AutoDiagnose still runs when no AutoFix mission exists.
The agent diagnoses the failure and either retries or opens a pull request, with the result shown inline on the job view. Configurable at organization, stack, namespace or module scope like every other mission type.
Governed integrations
An Integration entity (Slack first) with connection credentials stored encrypted in the organization's vault; the API never exposes raw credentials.
Delivery uses the same supply/demand model as runners and agents: per-scope integration events declare demand, per-scope integration supplies declare which scopes an integration serves, and delivery requires both. An is_supplied_to_all_modules flag covers the org-wide case. Credentials are cached per instance for 15 minutes and invalidated across instances on integration changes.
Assignment to Supply rename
Agent and runner assignments are renamed to supplies throughout, making the supply/demand model consistent across runners, agents and the new integrations.
Breaking change
The rename changes resource names in the Terraform provider and the API. Existing configurations need updating.
Intelligent GitOps for Infrastructure as Code. Automate, orchestrate, and scale your infrastructure deployments with confidence.
© 2026 Snap CD. All rights reserved.