Azure/terraform-azurerm-avm-res-containerregistry-registry v0.9.0 on GitHub

Breaking Changes

Direct users of modules/cache-rule, modules/credential-set and modules/scope-map must now supply a non-null location, including when enable_telemetry=false. Root calls already forward the existing root location.
Direct modules/scope-map users now require Terraform >= 1.5.0, < 2.0.0 instead of >= 1.3.0, because telemetry uses plantimestamp() and terraform_data. The root, cache-rule and credential-set minima remain >= 1.8.
Root AzAPI changes from ~> 2.4 to ~> 2.12; cache-rule and credential-set change from >= 2.0, < 3.0 to ~> 2.12; scope-map newly requires AzAPI ~> 2.12. Refresh incompatible lockfiles. Root AzureRM remains >= 4.81.0, < 5.0.0.
Root and all three children enable subscription-scope deployment telemetry by default. Configure the intended AzAPI subscription and grant appropriate subscription-deployment lifecycle permissions, or disable telemetry. Root enable_telemetry is forwarded to its children; direct child callers must configure their own flag. Deployments contain no workload resources, but add deployment-history and plan-timestamp updates.
Root ModTM and telemetry-only Random requirements are removed. removed blocks request forgetting the old telemetry resources without destruction; actual historical-state migration was not exercised. Back up state and inspect the upgrade plan. Naming examples still legitimately consume Random through the ModTM-free Naming module.

fix: allow cache rules and credential sets on every SKU by @myaschmitz in #233
feat: add azuread_authentication_as_arm_policy_enabled input by @myaschmitz in #234

docs: correct spelling in anonymous_pull_enabled description by @myaschmitz in #208
feat(metadata): add approved module metadata by @jaredfholgate in #226
fix: align scope map Terraform minimum by @jaredfholgate in #241

Full Changelog: v0.8.0...v0.9.0