This merge request will be published in a self-managed GitLab release. This label is added using the Release Tools project, and should not be manually added to merge requests.

Issues with this label are regressions from the previous non-patch release

Regression introduced in master (not yet released)

Features that will be included in the monthly release blog post

Generates a 'deprecation' release post item for this issue in the www-gitlab-com project

Release post item for this issue is in review

Release post item for this issue has been merged

Generates a 'primary' release post item for this issue in the www-gitlab-com project

Generates a 'removal' release post item for this issue in the www-gitlab-com project

Generates a 'secondary' release post item for this issue in the www-gitlab-com project

Generates a 'top' release post item for this issue in the www-gitlab-com project

An issue or a task blocking a release, either auto_deploy or customer packages

Issues in triage to be worked on by Release UX team

As a merge request is included in self-managed releases, it will receive the released::candidate label when the release candidate it is included in is deployed to pre.gitlab.com. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2

A merge request will receive the released::published label when included in a packaged release, such as 13.6.0 or 13.5.2, and deployed to release.gitlab.net for both automated and manual testing. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2

Release Post Managers can use this to track post entries they have already reviewed.

Subscribes the issue for automatic notifications related to security releases. This label is meant for use on Security Implementation Issues on the security mirror projects.