Skip to content

Release Version v3.8.0-gitlab

Bug Fixes

  • handlers: deny pushes for manifest lists with blob references except manifest cache images (79e854a)
  • handlers: enable cross repository blob mounts without FS mirroring (98fe521)
  • handlers: handle blob not found errors when serving head requests (2492b4e)
  • storage: never write blob links when FS mirroring is disabled (0786b77)

Features

  • datastore: allow removing a connection from the pool after being idle for a period of time (0352cc3)
  • storage/driver/s3-aws: add IRSA auth support (de69331)

Performance Improvements

  • handlers: lookup single blob link instead of looping over all (46f1642)

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

Generate a new release (documentation).

3. Update

  1. Version bump in CNG:
  2. Versions bumps for specific distribution paths:
    • Version bump in Omnibus:
      • Update version in config/software/registry.rb and use the Changelog: changed commit trailer in the commit message
      • Label merge request with: /label ~"workflow::ready for review" ~"feature::maintenance"
    • Version bump in Charts:
      • Wait for the Gitlab Dependency Bot to create a merge request for the new version of the registry
      • Update version and appVersion in charts/registry/Chart.yaml and use the Changelog: changed commit trailer in the commit message
      • Label merge request with: /label ~"workflow::ready for review"
    • Version bump in K8s Workloads:
      • Update $registry_version in init-values.yaml.gotmpl
      • Update tag in gstg.yaml.gotmpl
      • Label merge request with: /label ~"Service::Container Registry" ~"group::distribution" ~"devops::enablement" ~"workflow::ready for review"
      • Assign to a reviewer
Instructions

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

The CNG image is the pre-requisite for the remaining version bumps which may be merged independently from each other. Only CNG and K8s Workloads version bumps are required for a GitLab.com deployment. The deployment is then completed as documented here. Charts and Omnibus version bumps are required for self-managed releases.

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.

Note: According to the Distribution Team Merge Request Handling documentation, we should not assign merge requests to an individual.

Merge Request Template

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

Branch Name

bump-container-registry-vX-Y-Z-gitlab

Commit Message
Bump Container Registry to vX.Y.Z-gitlab

Changelog: changed
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-YYYY-MM-DD)

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

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