Skip to content

Release Version v3.18.1-gitlab

3.18.1 (2021-12-10)

Bug Fixes

  • revert enable PostgreSQL pageinspect extension (2c2825c)

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. If the change is not time sensitive and we are not close to the monthly GitLab release date (more than a week before), you may wait for the Gitlab Dependency Bot to create a version bump MR (example). You should then associate that MR with this release issue for visibility. Otherwise, please proceed as follows:
    • Version bump in K8s Workloads. This requires two separate MRs, one for pre-production and staging and another for production, which need to be created and merged in this order. Allow enough time between the two to confirm that everything is working as expected in pre-production and staging. For all environments, update registry_version under the respective stanza for each environment in bases/environments.yaml:
      • Pre-production and staging
        • Update registry_version under pre and gstg
        • Label with: /label ~"Service::Container Registry" ~"team::delivery" ~"workflow::ready for review"
        • Assign to a reviewer
      • Production
        • Update registry_version under gprd
        • Label with: /label ~"Service::Container Registry" ~"team::delivery" ~"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