Merge branch 'banhartt-fix-versions-doc-sections-order' into 'master'

Fix the order of the update sections

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/165618



Merged-by: Achilleas Pipinellis <axil@gitlab.com>
Approved-by: Achilleas Pipinellis <axil@gitlab.com>
Co-authored-by: Thorsten Banhart <thorsten.banhart@sick.de>

doc/update/versions/gitlab_17_changes.md

@@ -117,17 +117,6 @@ For more information, see the:
 - [Deprecations and removals documentation](../../update/deprecations.md#non-expiring-access-tokens).
 - [Deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/369122).
 
-## 17.4.0
-
-- Starting with GitLab 17.4, new GitLab installations have a different database schema regarding ID columns.
-  - All previous integer (32 bits) ID columns (for example columns like `id`, `%_id`, `%_ids`) are now created as `bigint` (64 bits).
-  - Existing installations will migrate from 32 bit to 64 bit integers in later releases when database migrations ship to perform this change.
-  - If you are building a new GitLab environment to test upgrades, install GitLab 17.3 or earlier to get
-    the same integer types as your existing environments. You can then upgrade to later releases to run the same
-    database migrations as your existing environments. This isn't necessary if you're restoring from backup into the
-    new environment as the database restore removes the existing database schema definition and uses the definition
-    that's stored as part of the backup.
-
 ## Issues to be aware of when upgrading from 17.1 and earlier
 
 - If the customer is using GitLab Duo and upgrading to GitLab 17.2.3 or earlier, they must do both of the following:
@@ -211,6 +200,17 @@ bits with a `certificate key too weak` error message.
 Check the [GitLab documentation on securing your installation](../../security/index.md).
 for more details.
 
+## 17.4.0
+
+- Starting with GitLab 17.4, new GitLab installations have a different database schema regarding ID columns.
+  - All previous integer (32 bits) ID columns (for example columns like `id`, `%_id`, `%_ids`) are now created as `bigint` (64 bits).
+  - Existing installations will migrate from 32 bit to 64 bit integers in later releases when database migrations ship to perform this change.
+  - If you are building a new GitLab environment to test upgrades, install GitLab 17.3 or earlier to get
+    the same integer types as your existing environments. You can then upgrade to later releases to run the same
+    database migrations as your existing environments. This isn't necessary if you're restoring from backup into the
+    new environment as the database restore removes the existing database schema definition and uses the definition
+    that's stored as part of the backup.
+
 ## 17.3.0
 
 - Git 2.45.0 and later is required by Gitaly. For installations from source, you should use the [Git version provided by Gitaly](../../install/installation.md#git).