Compatibility chart update

What does this MR do?

Updates Compatibility chart in accordance with the recently done changes.

Related issues

-

Author's checklist

• Consider taking the GitLab Technical Writing Fundamentals course
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• Ensure that the product tier badge is added to topic's h1.
• Request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are only adding documentation, do not add any of the following labels:

• ~"feature"
• ~"frontend"
• ~"backend"
• ~"bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Review 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 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.
  • 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 like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
• Ensure a release milestone is set.

@kutelev

Thank you for your contribution to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!

Some contributions require several iterations of review and we try to mentor contributors during this process. However, we understand that some reviews can be very time consuming. If you would prefer for us to continue the work you've submitted now or at any point in the future please let us know.

If you're okay with being part of our review process (and we hope you are!), there are several initial checks we ask you to make:

• The merge request description clearly explains:
  • The problem being solved.
  • The best way a reviewer can test your changes (is it possible to provide an example?).
• If the pipeline failed, do you need help identifying what failed?
• Check that Go code follows our Go guidelines.
• Read our contributing to GitLab Runner document.

This message was generated automatically. You're welcome to improve it.

added Community contribution label

Hi @gitlab-com/runner-docs-maintainers, please review this documentation Merge Request.

added documentation twtriaged labels

added 1 commit

• d3551568 - Compatibility chart update

Compare with previous version

@kutelev thanks! One suggestion

added Technical Writing docsfeature labels

added grouprunner label

mentioned in commit kutelev/gitlab-runner@34ffc360

added 1 commit

• 34ffc360 - As per: !3141 (comment 688596798)

Compare with previous version

assigned to @kutelev

added twdoing label and removed twtriaged label

resolved all threads

resolved all threads

added 1 commit

• 583c946f - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

changed milestone to %14.4

requested review from @ngaskill

Setting label(s) Category:Runner sectionops based on grouprunner.

added [Deprecated] Category:Runner sectionops labels

approved this merge request

requested review from @msedlakjakubowski

approved this merge request

Approving and setting to merge because Nick became a co-author and can no longer do it.

started a merge train

merged

mentioned in commit fe5e92d6

added typemaintenance label