[katbyte]

The changelog gets its v0.12.0 section, dated today, and every older entry is rewritten as one short plain sentence.

Why: the entries had grown into paragraphs of options, examples and mechanics. A changelog should say what changed for someone using the linter. The detail lives in each rule's README.

The next version. The unreleased entries become v0.12.0: five new acceptance-test rules, listed in rule order.

-## Unreleased
+## v0.12.0 (2026-10-09)
-- add rule `AZT006`: tests named for an update step must apply two different configs; one config, or the same config twice, never runs the update; report only, no fix ([#69](https://github.com/katbyte/azproviderlint/pull/69))
+- add rule `AZT006`: update tests that never update anything ([#69](https://github.com/katbyte/azproviderlint/pull/69))

Older entries, shortened. The same entries in the same order, in about a quarter fewer words.

-- add rule `AZG007`: struct literal fields set to their zero value should be omitted (named-constant zeros are kept); fixable with `-fix`; `tests` opts into test files ([#24](https://github.com/katbyte/azproviderlint/pull/24))
+- add rule `AZG007`: struct fields set to the value they would have anyway ([#24](https://github.com/katbyte/azproviderlint/pull/24))
-- `AZR003`: typed Delete reads through a local alias of `metadata.ResourceData` (`d := metadata.ResourceData; d.Get(...)`) are reported
+- `AZR003`: reads made through a renamed copy of the resource data are now reported

Things that are fine as they are. Every heading, date, rule number and link is unchanged, and no entry was added or dropped. That was checked section by section with a script. Option names stay only where the entry is about the option itself. AZT005 is not in this release.