Release 18.2.4 (18.2.3 was abandoned)

Preparation

Stable branches for GitLab Managed Versioning projects are required to have a green pipeline to perform a patch release. For each of the following branches verify the pipeline is green:

• GitLab
  • 18-2-stable-ee
• cng-ee
  • 18-2-stable
• gitaly
  • 18-2-stable
• gitlab-pages
  • 18-2-stable
• omnibus-gitlab-ee
  • 18-2-stable

If a failure is found the resolution process differs between each project:

• For GitLab project failures, follow the broken stable branch process.
• For GitLab components, contact the maintainers and notify them about the failure.

• Ensure that any post-deploy migrations in the stable branch have been executed on GitLab.com by executing the post-deploy migration pipeline: /chatops run post_deploy_migrations execute.

Packaging

• Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag. Note. If GitLab Canonical to Security mirroring has diverged on the default branch due to security merges this mirror is expected to show as a broken and can be safely ignored.

  /chatops run mirror status

• Tag 18.2.4 and confirm the job has finished:

  /chatops run release tag 18.2.4

• Make sure the backport MRs for https://gitlab.com/gitlab-org/release/tasks/-/issues/20903 are merged

  • gitlab-org/omnibus-gitlab!8658 (merged)
  • gitlab-org/build/CNG!2619 (merged)
  • gitlab-org/gitlab!201780 (merged)

• Tag 18.2.4 and confirm the job has finished: https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/19836302

  /chatops run release tag 18.2.4

• While waiting for packages to build, review and complete the blog post. => gitlab-com/www-gitlab-com!140670 (merged)

  • If the blog post failed to generate, it can be generated manually from the release-tools project with rake release:patch_release_blog_post.

• Check the progress of the EE/CE packages:

  • EE: 18.2.4+ee.0
  • CE: 18.2.4+ce.0

Note this may take a while (around 80 minutes).

Deploy

• For patch releases, the only available environment for deploys is release.gitlab.net. All GitLab Inc. team members can login to that installation using their email address (through google oauth).
• Deployment to release.gitlab.net will only be performed for the current release version. If a previous version is being released, you can move to the next section and begin publishing.

release.gitlab.net

• Deployments to release.gitlab.net are performed automatically.

Instructions to manually deploy if required.

If you need to manually run a deployment, you can do so as follows:

/chatops run deploy 18.2.4-ee.0 release

• Verify the deployment to release.gitlab.net has successfully completed. A slack notification will be posted in #announcements.

Release

• Publish the packages via ChatOps: https://ops.gitlab.net/gitlab-org/release/tools/-/jobs/19838471

  /chatops run publish 18.2.4

• Verify that the chatops publish pipeline created by running the above command succeeded.

• Retry any failed pipelines for 18.2.4. Chatops job logs: <Paste the chatops publish command CI pipeline URL here for easy access>

• Verify the check-packages job completes successfully on the EE Pipeline

• Verify the check-packages job completes successfully on the CE Pipeline

• Verify that Docker images appear on hub.docker.com: EE / CE

Final steps

• Merge the blog post.

• Notify the patch release has been published (blog post link needs to be replaced with the actual link).

  /chatops run notify ":mega: GitLab Patch Release:  has just been released: <blog post link>! Share this release blog post with your network to ensure broader visibility across our community.
  When is the next Release? Check it on the 'Release Information' dashboard: https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1"

• Create the 18.2.4 version on version.gitlab.com.

Release Certification

The release certification process may apply to this release. cc @gitlab-com/gl-security/product-security/federal-application-security