Announce deprecation of Code Suggestions v2 and v3 endpoints

Mike Wronskirequested to merge
598417-deprecate-aigw-v2-v3-endpoints into master

Be sure to link this MR to the relevant deprecation issue(s).

What does this MR do?

The /v4/code/suggestions endpoint replaces the AI Gateway v2 and v3 Code Suggestions endpoints. GitLab plans to remove the old endpoints in 21.0. No entry existed under data/deprecations, so the removal had no formal announcement. The deprecation issue and the breaking change approval planned the announcement for 19.1, but it did not happen.

One new deprecation entry announces the change. The announcement milestone is 19.5 and the removal milestone is 21.0. It is a breaking change with low impact for GitLab Self-Managed and GitLab Dedicated; GitLab.com is not affected. The compiled deprecations page has the same entry.

Only tools that call the gateway directly with the old endpoints are affected: instances on a GitLab version that still calls v2 or v3, outdated IDE extensions, and custom clients.

Note for reviewers: if this MR merges after the 19.5 documentation cut, the file name and the announcement milestone move to 19.6.

EM/PM release post item checklist

  • Set yourself as the Assignee, meaning you are the DRI.
  • For breaking changes: the breaking change label is on the MR. window stays empty because GitLab.com is not affected.
  • Confirm this MR is labeled release post itemdeprecation
  • Follow the process to create a deprecation YAML file.
  • Add reviewers by the 10th.
  • Add scoped devops:: and group:: labels as necessary.
  • Add the appropriate milestone to this MR.
  • When ready to be merged (and no later than the 15th) @mention the TW for final review and merge.

Reviewers

  • (Recommended) PMM
  • (Optional) Product Designer
  • (Optional) Group Manager or Director
  • Required review and approval: Technical Writer designated to the corresponding DevOps stage/group

Merge request reports