Rollout of Ruby 3.3 package to production

Proposal

Following up from the results of the test rollout(s) in #21665 (closed), this issue is to plan and keep track of the Ruby 3.3 rollout to production.

We can expect to use the steps documented in https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/ruby-upgrades.md.

Pause auto-deployments

Similar to the previous Ruby rollout to production, this procedure is estimated to take around 6 hours to complete.

During this process, auto-deployments should be paused and no other packages should be deployed to any of the environments.

Difference between the test rollout vs production rollout

The main differences are:

• We will be setting the USE_NEXT_RUBY_VERSION_IN_AUTODEPLOY variables on the project level, instead of the pipeline level.
• Rollback procedures are necessary for production and staging failures.
  • The above project level variables need to be unset
  • Chatops rollback commands need to be run

Refer to the previous Ruby rollout CR:

• 3.1: production#17201 (closed)
• 3.2: production#18519 (closed)

Change Request

This issue is to keep track of release management and general grouprelease-and-deploy discussion and planning. Create a followup CR. That CR will be the SSOT for the details of the rollout.

CR: production#21065 (closed)