# Release notes 0.1.172

> 29 October 2026: A fix release for reverting an unauthorized security-group change.

_Release notes · Updated 2026-10-29 · Describes release 0.1.173_

## 0.1.172 — 29 October 2026 {#0-1-172-29-october-2026}

A fix release for reverting an unauthorized security-group change. No schema change, no new route, setting or audit action.

### Typed revoke without an AWS Config record {#typed-revoke-without-an-aws-config-record}

- **An added security-group rule is reverted by its rule id even when AWS Config does not record security groups.** In an account whose Config recorder leaves out `AWS::EC2::SecurityGroup`, a hand-made `AuthorizeSecurityGroupIngress` had no before-state, so its revert was a by-hand step although CloudTrail named the `sgr-` id it added. The revert is now a typed revoke of exactly those rule ids, in the drafted revert of an unauthorized change and in **Draft revert**; a rule CloudTrail named no id for stays a by-hand step. Later changes on the group are left as they are.


## Next steps

- Next: [Release notes 0.1.171](/help/release-notes-0-1-171.md)
- [All What's new pages](/help/what-s-new/llms.txt)
- [Documentation home](/help/)