Release 3.32.2 documentation (#1388)

* docs: Release 3.32.2

* doc: Add `v3.32.2` featured section

---------

Co-authored-by: Aleksander Borowski <aleksander.borowski@thethingsindustries.com>

doc/config/_default/config.toml

@@ -23,7 +23,7 @@ pygmentsUseClasses = true
   github_repository = "https://github.com/TheThingsIndustries/lorawan-stack-docs"
   github_repository_edit = "https://github.com/TheThingsIndustries/lorawan-stack-docs/blob/master/doc/content"
   tts_github_repository = "https://github.com/TheThingsNetwork/lorawan-stack"
-  version = "3.32.1"
+  version = "3.32.2"
 
 [markup]
   [markup.goldmark]

doc/content/the-things-stack/host/aws/ecs/changelog/index.md

@@ -2,12 +2,21 @@
 title: "Template Changelog"
 aliases: [/getting-started/aws/ecs/changelog]
 ---
-
 # Upgrading
 
-## 3.32.1
+All meaningful changes to templates are documented in this file.
 
-- Updated ECS AMIs to the latest versions.
+## Unreleased
+
+- Add GRPC methods rate limiting metric to prometheus rules.
+
+### AMI/BYOL template
+
+- Add a new `TLSCertificateSecretARN` parameter to allow loading TLS certificates from AWS secrets to BYOL and PAYG single template deployments.
+- Add new IAM policy role that allows reading secrets from AWS Secret Manager
+- Update default postgres version to 16.4
+
+## 3.32.1
 
 ## 3.32.0
 

doc/content/whats-new/3.32.2.md

@@ -0,0 +1,23 @@
+---
+date: 2024-11-18T21:25:11Z
+title: "3.32.2"
+featured:
+  {
+    fixed:
+      [
+        "Potential leak of end devices of other (owned) applications in the top end devices panel in the application overview of the Console.",
+      ],
+  }
+---
+
+### Fixed
+
+- Potential leak of end devices of other (owned) applications in the top end devices panel in the application overview of the Console.
+- Fix reversed Join Server dev nonce metrics.
+- Enforce default page limit on IS List RPCs if a value is not provided in the request.
+- Identity Server's store runs each migration within a transaction, so a migration's changes are only applied if all of its queries are successful.
+  - Identity Server's store now marks a migration as successful after all its operations are finished. Previously it was possible to have a successful migration which not all of its queries were processed.
+- Network Operation Center's store runs each migration within a transaction, so a migration's changes are only applied if all of its queries are successful.
+  - Network Operation Center's store now marks a migration as successful after all its operations are finished. Previously it was possible to have a successful migration which not all of its queries were processed.
+- Storage Integration's store runs each migration within a transaction, so a migration's changes are only applied if all of its queries are successful.
+  - Storage Integration's store now marks a migration as successful after all its operations are finished. Previously it was possible to have a successful migration which not all of its queries were processed.