- name: "Deprecate `pipelines` fields in the Package GraphQL types"
  announcement_milestone: "14.6" # The milestone when this feature was first announced as deprecated.
  announcement_date: "2021-12-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
  removal_milestone: "15.0" # The milestone when this feature is planned to be removed
  removal_date: "2022-05-22" # the date of the milestone release when this feature is planned to be removed
  breaking_change: true
  body: | # Do not modify this line, instead modify the lines below.
    As part of the work to create a [Package Registry GraphQL API](https://gitlab.com/groups/gitlab-org/-/epics/6318), the Package group deprecated the `pipelines` fields in all Package-related GraphQL types. As of GitLab 14.6, the `pipelines` field is deprecated in [`Package`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#package) and [`PackageDetailsType`](https://docs.gitlab.com/ee/api/graphql/reference/index.html#packagedetailstype) due to scalability and performance concerns.

    In milestone 15.0, we will completely remove `pipelines` from `Package` and `PackageDetailsType`. You can follow and contribute to work on a replacement in the epic [GitLab-#7214](https://gitlab.com/groups/gitlab-org/-/epics/7214).
  stage: package
  tiers: Free
  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/347219