Adds 3.12.2 release notes (#1178)

Co-authored-by: Steven Smith <[email protected]>

modules/attributes.adoc

@@ -15,7 +15,7 @@ ifeval::["{productname}" == "Project Quay"]
 :productname: Project Quay
 :productversion: 3
 :producty: 3.13
-:productminv: v3.13.1
+:productminv: v3.13.2
 :productrepo: quay.io/projectquay
 :quayimage: quay
 :clairimage: clair
@@ -32,8 +32,8 @@ ifeval::["{productname}" == "Red Hat Quay"]
 :productversion: 3
 :producty: 3.13
 :producty-n1: 3.12
-:productmin: 3.13.1
-:productminv: v3.13.1
+:productmin: 3.13.2
+:productminv: v3.13.2
 :productrepo: registry.redhat.io/quay
 :clairnewver: v3.13
 :quayimage: quay-rhel8

modules/rn_3_13_0.adoc

@@ -4,6 +4,22 @@
 
 The following sections detail _y_ and _z_ stream release information.
 
+[id="rn-3-13-2"]
+== RHBA-2024:10967 - {productname} 3.13.2 release
+
+Issued 2024-12-12
+
+{productname} release 3.13.2 is now available with Clair {clairproductminv}. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2024:10967[RHBA-2024:10967] advisory. 
+
+[id="bug-fixes-313-2"]
+=== {productname} 3.13.2 bug fixes
+
+* link:https://issues.redhat.com/browse/PROJQUAY-8273[PROJQUAY-8273],link:https://issues.redhat.com/browse/PROJQUAY-6474[PROJQUAY-6474]. When deploying {productname} with an custom `HorizontalPodAutoscaler` component and then setting the component to `managed: false` in the `QuayRegistry` custom resource definition (CRD), the {productname} Operator continuously terminates and resets the `minReplicas` value to 2 for `mirror` and `clair` components. To work around this issue, see link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#operator-unmanaged-hpa[Using unmanaged Horizontal Pod Autoscalers].
+
+* link:https://issues.redhat.com/browse/PROJQUAY-8208[PROJQUAY-8208]. Previously, {productname} would return a `501` error on repository or organization creation with the authorization type was set to OIDC and restricted users were set. This issue has been resolved.
+
+* link:https://issues.redhat.com/browse/PROJQUAY-8269[PROJQUAY-8269]. Previously, on the {productnamne} UI, the OAuth scopes page suggested that scopes could be applied to robot accounts. This was not the case. Wording on the OAuth scopes page of the UI has been fixed.
+
 [id="rn-3-13-1"]
 == RHBA-2024:9478 - {productname} 3.13.1 release