Release notes 0.1.169
29 October 2026: A fix release.
Release notes · Updated 2026-10-29 · Describes release 0.1.171
0.1.169 — 29 October 2026
A fix release. A security-group rule that a person added by hand on a group managed by infrastructure-as-code now gets a proposed fix, and the estate view no longer lists Kubernetes objects twice after a cluster is added to a kubectl connection. No schema change, no new route, setting or audit action.
Hand-added rules on IaC-managed security groups
- A rule added by hand gets a revoke, even on an IaC-managed group. A
ManagedBy(Terraform, Terragrunt or CDK) tag says the security group is managed as code, not that the code declares every rule on it. The agent now treats a rule as repository-owned only when it read the rule in a repository file or the change history shows the IaC pipeline wrote it. A world-open rule that a person added live is drift: the agent proposes the revoke (the matching runbook when one exists), and checking the IaC with a clean plan becomes a follow-up action. A repository it cannot reach no longer leaves the incident without a fix. Checked by unit tests and the prompt golden files.
Kubernetes objects listed once after a cluster is added
- Adding a cluster to a kubectl connection no longer duplicates the estate. Adding a cluster config changes the id of every Kubernetes object that connection reads. The next harvest kept the objects under the old ids beside the new ones, so each service group showed every Service, Workload, Pod, Node and Cluster twice. The harvest now drops that connection's objects under ids it no longer reads; earlier versions of the estate keep them as history. Checked by unit tests.