Clarify required steps in upgrade paths
What does this MR do?
Clarifies that 13.5.3 is not a required step in the upgrade path.
13.5.3 was added because it was the latest version available at the time the docs was written. The versions are hard-coded, not dynamically updated.
This MR changes the final step to be 13.x (latest), which is true at the time of writing and it will remain true for a few months (when we update docs to add the 14.x release)
@axil WDYT?
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team