Remove documentation references to pre-17.0 versions of GitLab

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

Point 3 from #6431 (closed)

Thanks for your contribution to GitLab @heidi.berry!

• If you need help, page a coach by clicking here or come say hi on Discord.
• When you're ready, request a review by clicking here.
• We welcome AI-generated contributions and offer complimentary access to GitLab Duo!
• To add labels to your merge request, comment @gitlab-bot label ~"label1" ~"label2".

This message was generated automatically. Improve it or delete it.

added Community contribution workflowin dev labels

assigned to @heidi.berry

changed the description

	2 Warnings
	a6bf6d94: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@tigerwnz (UTC+13)	@timofurrer (UTC+1)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added linked-issue label

@gitlab-bot ready

Posted via contributors.gitlab.com.

added workflowready for review label and removed workflowin dev label

Hi @PatrickRice! Please review this documentation merge request. This message was generated automatically. Improve it or delete it.

added documentation twtriaged labels

requested review from @PatrickRice

@PatrickRice, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
• If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
• Please ensure the group's Product Manager has validated the linked issue.

This message was generated automatically. Improve it or delete it.

approved this merge request

@PatrickRice, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, please start a new pipeline before merging.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

added pipeline:mr-approved label

Thanks @heidi.berry !

resolved all threads

changed milestone to %17.9

started a merge train

	1 Warning
	a6bf6d94: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@tigerwnz (UTC+13)	@timofurrer (UTC+1)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

mentioned in commit 33447fa0

merged

added typemaintenance label

Hi @heidi.berry

See where you rank! Check your spot on the contributor leaderboard and unlock rewards.

---

How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

Thanks for your help!

This message was generated automatically. Improve it or delete it.