quay · stevsmit · Mar 10, 2023 · Mar 10, 2023
diff --git a/modules/rn_3_80.adoc b/modules/rn_3_80.adoc
@@ -1,40 +1,53 @@
 :_content-type: CONCEPT
 
+[id="rn-3-804"]
+= RHBA-2023:1188 - {productname} 3.8.4 bug fix update
+
+Issued 2023-3-14
+
+{productname} release 3.8.4 is now available. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2023:1188[RHBA-2023:1188] advisory.
+
+[id="bug-fixes-384"]
+== Bug fixes
+
+* link:https://issues.redhat.com/browse/PROJQUAY-5074[PROJQUAY-5074]. Health checks should check storage engines.
+* link:https://issues.redhat.com/browse/PROJQUAY-5117[PROJQUAY-5117]. Quay calls LDAP on robot account login.
+
 [id="rn-3-803"]
-== RHBA-2023:0906 - {productname} 3.8.3 bug fix update
+= RHBA-2023:0906 - {productname} 3.8.3 bug fix update
 
-Issues 2023-2-27
+Issued 2023-2-27
 
 {productname} release 3.8.3 is now available. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2023:0906[RHBA-2023:0906] advisory.
 
 [id="bug-fixes-383"]
-=== Bug fixes
+== Bug fixes
 
 * link:https://issues.redhat.com/browse/PROJQUAY-3643[PROJQUAY-3643]. CVE-2022-24863 quay-registry-container: http-swagger: a denial of service attack consisting of memory exhaustion on the host system [quay-3.7]
 
 [id="rn-3-802"]
-== RHBA-2023:0789 - {productname} 3.8.2 bug fix update
+= RHBA-2023:0789 - {productname} 3.8.2 bug fix update
 
 Issued 2023-2-15
 
 {productname} release 3.8.2 is now available with Clair 4.6.0. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2023:0789[RHBA-2023:0789] advisory.
 
 [id="bug-fixes-382"]
-=== Bug fixes
+== Bug fixes
 
 * link:https://issues.redhat.com/browse/PROJQUAY-4395[PROJQUAY-4395]. Default value of `false` for `CLEAN_BLOB_UPLOAD_FOLDER` does not make sense.
 * link:https://issues.redhat.com/browse/PROJQUAY-4726[PROJQUAY-4726]. No audit logs when superuser trigger and cancel build under normal user's namespace with superuser full access enabled.
 * link:https://issues.redhat.com/browse/PROJQUAY-4992[PROJQUAY-4992]. Cleanup deprecated appr code.
 
 [id="rn-3-801"]
-== RHBA-2023:0044 - {productname} 3.8.1 bug fix update
+= RHBA-2023:0044 - {productname} 3.8.1 bug fix update
 
 Issued 2023-1-24
 
 {productname} release 3.8.1 is now available. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2023:0044[RHBA-2023:0044] advisory.
 
 [id="bug-fixes-381"]
-=== Bug fixes
+== Bug fixes
 
 * link:https://issues.redhat.com/browse/PROJQUAY-2164[PROJQUAY-2146]. Combined URLs in security scan report (pointing to errata URL).
 * link:https://issues.redhat.com/browse/PROJQUAY-46674667[PROJQUAY-]. Web UI - viewing account results in error.
@@ -45,14 +58,14 @@ Issued 2023-1-24
 * link:https://issues.redhat.com/browse/PROJQUAY-4765[PROJQUAY-4765]. Quay 3.8.0 superuser does not have permission to add new team member to normal user's team when enabled superuser full access.
 
 [id="rn-3-800"]
-== RHBA-2022:6976 - {productname} 3.8.0 release
+= RHBA-2022:6976 - {productname} 3.8.0 release
 
 Issued 2022-12-6
 
 {productname} release 3.8.0 is now available with Clair 4.5.1. The bug fixes that are included in the update are listed in the link:https://access.redhat.com/errata/RHBA-2022:6976[RHBA-2022:6976] advisory.
 
 [id="new-features-and-enhancements-38"]
-=== {productname}, Clair, and Quay Builder new features and enhancements
+== {productname}, Clair, and Quay Builder new features and enhancements
 
 The following updates have been made to {productname}, Clair, and Quay Builders:
 
@@ -117,7 +130,7 @@ ALLOWED_OCI_ARTIFACT_TYPES:
 When adding OCI media types that are not configured by default, users will also need to manually add support for cosign and Helm if desired. The ztsd compression scheme is supported by default, so users will not need to add that OCI media type to their config.yaml to enable support.
 ====
 
-==== New {productname} configuration fields
+== New {productname} configuration fields
 
 * The following configuration field has been added to test {productname}'s new user interface:
 
@@ -179,7 +192,7 @@ For more information, see link:https://access.redhat.com/documentation/en-us/red
 For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3.8/html-single/configure_red_hat_quay/index#configuring-restricted-users-whitelist[RESTRICTED_USERS_WHITELIST configuration reference].
 
 [id="quay-operator-updates"]
-=== {productname} Operator
+== {productname} Operator
 
 The following updates have been made to the {productname} Operator:
 
@@ -200,10 +213,10 @@ For more information, see link:https://issues.redhat.com/browse/PROJQUAY-272[PRO
 For a list of known limitations, see xref:ipv6-limitations-38[IPv6 and dual-stack limitations].
 
 [id="known-issues-and-limitations-38"]
-=== {productname} 3.8 known issues and limitations
+== {productname} 3.8 known issues and limitations
 
 [id="known-issues-38"]
-==== Known issues:
+=== Known issues:
 
 * The `metadata_json` column in the `logentry3` table on MySQL deployments has a limited size of `TEXT`. Currently, the default size of the column set to be `TEXT` is 65535 bytes. 65535 bytes is not big enough for some mirror logs when debugging is turned `off`. When a statement containing `TEXT` larger than 65535 bytes is sent to MySQL, the data sent is truncated to fit into the 65535 boundary. Consequently, this creates issues when the `metadata_json` object is decoded, and the decode fails because the string is not terminated properly. As a result, {productname} returns a 500 error.
 +
@@ -289,7 +302,7 @@ DISTRIBUTED_STORAGE_CONFIG:
 ----
 
 [id="ipv6-limitations-38"]
-==== IPv6 and dual-stack limitations and known issues:
+=== IPv6 and dual-stack limitations and known issues:
 
 * Currently, attempting to configure your {productname} deployment with the common Azure Blob Storage configuration will not work on IPv6 single stack environments. Because the endpoint of Azure Blob Storage does not support IPv6, there is no workaround in place for this issue.
 +
@@ -310,12 +323,12 @@ For more information, see link:https://issues.redhat.com/browse/PROJQUAY-4470[PR
 * There is a known issue when  `FEATURE_LISTEN_IP_VERSION` is set to `IPv6`, and you have selected *{productname} handles TLS* in the configuration editor and uploaded self-signed certificates. If these conditions have been met, and you update any one configuration in the configuration editor (for example, adding a new superuser), when reconfiguring {productname} again, the mirror pod crashes and returns the following error: `Init:CrashLoopBackOff`. If *{productname} handles TLS* is selected in your deployment, you must set `FEATURE_LISTEN_IP_VERSION` to `IPv4`. This will be fixed in a future version of {productname}.
 
 [id="bug-fixes-38"]
-=== {productname} bug fixes
+== {productname} bug fixes
 
 * link:https://issues.redhat.com/browse/PROJQUAY-4431[PROJQUAY-4431]. Proxy cache failed to validate Azure Container Registry (ACR).
 
 [id="quay-feature-tracker"]
-=== {productname} feature tracker
+== {productname} feature tracker
 
 New features have been added to {productname}, some of which are currently in Technology Preview. Technology Preview features are experimental features and are not intended for production use.
 
@@ -434,7 +447,7 @@ Some features available in previous releases have been deprecated or removed. De
 |===
 
 [id="deprecated-features"]
-==== Deprecated features
+=== Deprecated features
 
 [id="docker-v1-support"]
 * Support for Docker v1 is now deprecated and will be removed in a future release of {productname}. Users must now opt-in to enable Docker v1 support. Users should migrate any stored images in Docker v1 format to the OCI image format to avoid potential loss of data.