Release notes 0.1.171
29 October 2026: A fix release for changes that need two approvals.
Release notes · Updated 2026-10-29 · Describes release 0.1.173
0.1.171 — 29 October 2026
A fix release for changes that need two approvals. No schema change, no new route, setting or audit action.
Approvals kept across an estate refresh
- An estate refresh no longer voids an approval already given when it only learns more about the change's own target. A refresh between the two approvals of a change could teach the platform about the resource the change touches, and the first approval was then treated as out of date. The approval now holds when the steps, connection, target and policy are unchanged and the change would cut off the same things. Anything the change would now cut off still asks for a new review. Checked by unit tests.