diff --git a/doc/update/versions/gitlab_18_changes.md b/doc/update/versions/gitlab_18_changes.md
index 5ce64199e1edcf50e675d3b0bda520a15676602f..3a8a7c1ff959f7a3503fa80880fd29461f1e7931 100644
--- a/doc/update/versions/gitlab_18_changes.md
+++ b/doc/update/versions/gitlab_18_changes.md
@@ -29,7 +29,11 @@ For additional information for Helm chart installations, see
 
 ### Geo installations 18.1.0
 
-- GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.1 or later.
+- GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.2 or later.
+- GitLab versions 18.1.0 and 18.1.1 show errors in the PostgreSQL logs such as `ERROR:  relation "ci_job_artifacts" does not exist at ...`.
+
+  These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later.
+  For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954).
 
 ## 18.0.0
 
@@ -58,6 +62,11 @@ For additional information for Helm chart installations, see
 
 - GitLab versions 18.0 through 18.0.2 have a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.0.3 or later.
 
+- GitLab versions 18.0 through 18.0.2 show errors in the PostgreSQL logs such as `ERROR:  relation "ci_job_artifacts" does not exist at ...`.
+
+  These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later.
+  For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954).
+
 ### PRNG is not seeded error on Docker installations
 
 If you run GitLab on a Docker installation with a FIPS-enabled host, you