Remove beta status from Rapid Diffs docs
What does this MR do?
This MR removes the beta status and the missing-features note from the Rapid Diffs section of the merge request changes docs, and adds a history entry saying Rapid Diffs is generally available in GitLab 19.6.
Rapid Diffs is now the only diff experience on the merge request Changes tab: its feature flags and the option to switch back to classic diffs are all removed in 19.6. Calling it beta no longer matches what users get, so this MR also drops the note that some classic diff features are missing. The links to the feedback issue and the feature parity epic stay.
The Rapid Diffs UI has no beta or experimental labeling, so this MR changes only the docs. The 19.0 release post keeps its "(Beta)" title, because it describes the feature as it shipped then.
Related issues
Author's checklist
- Optional. Consider taking the GitLab Technical Writing Fundamentals course.
- Follow the:
- If you're adding a new page, add the product availability details under the H1 topic title. Not applicable: no new page.
- If you are a GitLab team member, request a review based on:
- The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"~"backend"~"type::bug"~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
- If the content requires it, ensure the information is reviewed by a subject matter expert.
- Technical writer review items:
- Ensure docs metadata is present and up-to-date.
- Ensure the appropriate labels are added to this MR.
- Ensure a release milestone is set.
- If relevant to this MR, ensure content topic type principles are in use, including:
- The headings should be something you'd do a Google search for. Instead of
Default behavior, say something likeDefault behavior when you close an issue. - The headings (other than the page title) should be active. Instead of
Configuring GDK, say something likeConfigure GDK. - Any task steps should be written as a numbered list.
- If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
- The headings should be something you'd do a Google search for. Instead of
- Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.