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/163881



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

@@ -87,6 +87,36 @@ For more information about upgrading GitLab Helm Chart, see [the release notes f
   the upgrade. This bug has been fixed with GitLab 17.1.2 and upgrading from GitLab 16.x directly to 17.1.2 will not
   cause these issues.
 
+### Linux package installations
+
+Specific information applies to Linux package installations:
+
+- The binaries for PostgreSQL 13 have been removed.
+
+  Prior to upgrading, you must ensure your installation is using
+  [PostgreSQL 14](https://docs.gitlab.com/omnibus/settings/database.html#upgrade-packaged-postgresql-server).
+
+### Non-expiring access tokens
+
+Access tokens that have no expiration date are valid indefinitely, which is a
+security risk if the access token is divulged.
+
+When you upgrade to GitLab 16.0 and later, any [personal](../../user/profile/personal_access_tokens.md),
+[project](../../user/project/settings/project_access_tokens.md), or
+[group](../../user/group/settings/group_access_tokens.md) access
+token that does not have an expiration date automatically has an expiration
+date set at one year from the date of upgrade.
+
+Before this automatic expiry date is applied, you should do the following to minimize disruption:
+
+1. [Identify any access tokens without an expiration date](../../security/tokens/token_troubleshooting.md#find-tokens-with-no-expiration-date).
+1. [Give those tokens an expiration date](../../security/tokens/index.md#extend-token-lifetime).
+
+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).
+
 ## Issues to be aware of when upgrading from 17.3
 
 - Migration failures when upgrading from GitLab 17.3.
@@ -136,36 +166,6 @@ For more information about upgrading GitLab Helm Chart, see [the release notes f
    agent_configs_to_remove.delete_all
    ```
 
-### Linux package installations
-
-Specific information applies to Linux package installations:
-
-- The binaries for PostgreSQL 13 have been removed.
-
-  Prior to upgrading, you must ensure your installation is using
-  [PostgreSQL 14](https://docs.gitlab.com/omnibus/settings/database.html#upgrade-packaged-postgresql-server).
-
-### Non-expiring access tokens
-
-Access tokens that have no expiration date are valid indefinitely, which is a
-security risk if the access token is divulged.
-
-When you upgrade to GitLab 16.0 and later, any [personal](../../user/profile/personal_access_tokens.md),
-[project](../../user/project/settings/project_access_tokens.md), or
-[group](../../user/group/settings/group_access_tokens.md) access
-token that does not have an expiration date automatically has an expiration
-date set at one year from the date of upgrade.
-
-Before this automatic expiry date is applied, you should do the following to minimize disruption:
-
-1. [Identify any access tokens without an expiration date](../../security/tokens/token_troubleshooting.md#find-tokens-with-no-expiration-date).
-1. [Give those tokens an expiration date](../../security/tokens/index.md#extend-token-lifetime).
-
-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.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).