Release Version v3.72.0-gitlab
What's New in this Version
3.72.0 (2023-05-02)
Bug Fixes
- datastore: importer: consistently store config blob media types in database (4cf8c52)
- datastore: importer: consistently store layer blob media types in database (fc7ce4b)
- datastore: importer: display counters for new import methods (27cfc44)
- gc: ignore broken tag link (db3d8d7)
Features
- api/gitlab/v1: add config digest to List Repository Tags response (299fa44)
- azure: introduce azure storage driver legacyrootprefix config (4314deb)
- database: use service discovery for primary address (8fcbca0)
- handlers: remove online migration routes (0fb586a)
- proxy: remove pull-through proxy cache feature (557061d)
- remove migration path label from storage metrics (f7c9402)
Performance Improvements
- add uber automaxprocs package (873ae97)
Tasks
All tasks must be completed (in order) for the release to be considered workflowproduction.
1. Prepare
-
Set the milestone of this issue to the target GitLab release. -
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
-
Version bump in CNG is automatically done using the internal release-cli
. An MR should be found open on the CNG MR page after manually triggering theversion-bump:cng
job. If opening this MR manually please give it the title "Update gitlab-org/container-registry [version]". -
Version bumps for specific distribution paths: -
Version bump in Omnibus is automatically done using the internal release-cli
. An MR should be found open on the Omnibus MR page after manually triggering theversion-bump:omnibus
job (which requiresversion-bump:cng
to be triggered first). If opening this MR manually please give it the title "Update gitlab-org/container-registry [version]". -
Version bump in Charts is automatically done using the internal release-cli
. An MR should be found open on the Charts MR page after manually triggering theversion-bump:charts
job (which requiresversion-bump:cng
to be triggered first). If opening this MR manually please give it the title "Update gitlab-org/container-registry [version]". -
Version bump in K8s Workloads is automatically done using the internal release-cli
. There should be two separate MRs, one for Pre-production and Staging and another for Production, on the K8s Workloads MR page after manually triggering theversion-bump:k8s
job (which requiresversion-bump:cng
to be triggered first). If opening this MR manually please give it the title "Bump Container Registry to [version]".
-
-
Version bump for GDK is automatically done using the internal release-cli
. An MR should be found open on the GDK MR page after manually triggering theversion-bump:gdk
job (which requiresversion-bump:cng
to be triggered first). If opening this MR manually please give it the title "Bump Container Registry to [version]".-
Assign to the reviewer suggested by reviewer roulette
-
Instructions
Bump the Container Registry version used in CNG, Omnibus, Charts and K8s Workloads by manually triggering these on the release
job.
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.
Please 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 when updating manually, 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
-
Assign label workflowverification once all changes have been merged. -
Assign label workflowproduction once all changes have been deployed. -
Update all related issues, informing that the deploy is complete. -
Close this issue.
Instructions
To see the version deployed in each environment, look at the Grafana Container Registry dashboard:/label devopspackage groupcontainer registry Category:Container Registry golang workflowscheduling