Skip to content

Remove removal that won't be removed from blog

Tim Rizzi requested to merge trizzi-master-patch-52912 into master

Why is this change being made?

Since the merging of the breaking change blog post the package group has figured out a way to avoid the removal of https://about.gitlab.com/blog/2022/04/18/gitlab-releases-15-breaking-changes/#pipelines-fields-in-the-package-graphql-types. As such, I wanted to remove it from the blog post so as not to be confusing.

The good news, it's already removed from the deprecations and removals from the gitlab.org project.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
  • Assign reviewers for this change to the correct DRI(s)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports