Announce removal of secretPermission GraphQL mutations

Chaya Danzingerrequested to merge
docs-630579-deprecate-secret-permission-mutations into master

Announces the 19.5 removal of the secretPermissionUpdate and secretPermissionDelete GraphQL mutations. projectSecretsPermissionUpdate and projectSecretsPermissionDelete replace them.

The code removal is a separate merge request so it can follow the normal backend review path. This announcement must merge first, so the public record never trails the removal.

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

Why this is a one-step removal

GitLab Secrets Manager reaches General Availability in 19.5. The development stages policy allows a breaking change to a Beta feature outside a major release, so 19.5 is the last milestone where these mutations can be removed in one step. After General Availability, a removal needs a deprecation in one milestone and a removal in 20.0.

The two mutations carried no experiment marker in the GraphQL reference, so an API user could have adopted them between 17.11 and now. Internal use is nil. Product confirmed the removal.

Because of that timing, announcement_milestone and removal_milestone are both 19.5. There is precedent for this in data/deprecations/19-3-rest-api-non-numeric-ids.yml.

Breaking change window

The window: field is empty, which assigns this to the primary window. Set it if the release manager prefers the contingency window.

EM/PM release post item checklist

  • Set yourself as the Assignee, meaning you are the DRI.
  • For breaking changes:
    • Add the breaking change label to the MR.
    • If the breaking change affects GitLab.com, add window with a value of 1, 2, or 3. Left empty for the primary window; confirm with @swiskow if a specific window is needed.
  • 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.
  • If the changes modify log format(addition/deletion/modification) of product feature, tag the security logging team. Does not apply; this change does not alter log format.
  • When ready to be merged (and no later than the 15th) @mention the TW for final review and merge.

Reviewers

I already ran bin/rake gitlab:docs:compile_deprecations, so doc/update/deprecations.md is up to date in this branch.

References

Merge request reports