Release Version v2.8.2-gitlab

Issues

Merge Requests

Tasks

All tasks must be completed (in order) for the release to be considered workflowproduction.

1. Prepare

  1. Set the milestone of this issue to the target GitLab release.
  2. Set the due date of this issue to the 12th of the release month.
Instructions The due date is set to the 12th of each month to create a buffer of 5 days before the merge deadline on the 17th. See Product Development Timeline for more information about the GitLab release timings.

2. Release

  1. Create a merge request to add an entry to the changelog.
  2. Create a tag for the new release.
Instructions Please mention this issue in the description of the changelog merge request.

See release instructions for additional information.

3. Deploy

  1. Version bump in CNG:
  2. Version bump in Omnibus:
  3. Version bump in Charts:
  4. Version bump in K8s Workloads:
Instructions

Bump the Container Registry version used in CNG, Omnibus, Charts and K8s Workloads.

Create a merge request for each project. Mark parent tasks as completed once the corresponding merge requests are merged.

Version bump merge requests should appear automatically in the Related merge requests section of this issue.

Template

For consistency, please use the following template for these merge requests:

Title
Bump Container Registry to vX.Y.Z-gitlab
Description

Repeat the version subsection for multiple versions. As an example, to bump to v2.7.7 in a project where the current version is v2.7.5, create an entry for v2.7.6 and v2.7.7.

## vX.Y.Z-gitlab
[Changelog](https://gitlab.com/gitlab-org/container-registry/blob/release/X.Y-gitlab/CHANGELOG.md#vXYZ-gitlab)

Related to <!-- link to this release issue -->.
Changelog Entries

Some projects require a changelog entry, please use the following template whenever necessary:

---
title: Bump Container Registry to vX.Y.Z-gitlab
merge_request: # number (not the link) of the version bump merge request
author:
type: changed

4. Complete

  1. Assign label workflowverification once all changes have been merged.
  2. Assign label workflowproduction once all changes have been deployed.
  3. Update all related issues, informing that the deploy is complete.
  4. Close this issue.
Instructions To see the version deployed in each environment, look at the Grafana Container Registry dashboard:

image

Edited by João Pereira