Skip to content

Define the Ruby patch version to use in CI jobs

Rémy Coutable requested to merge fix-ruby-patch-version-for-17-0 into 17-0-stable-ee

What does this MR do and why?

This picks the following MRs in 17-0-stable-ee:

This should make !157213 (closed) not needed.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

  • This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
  • The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
  • This MR has a severity label assigned (if applicable).
  • Set the milestone of the merge request to match the target backport branch version.
  • This MR has been approved by a maintainer (only one approval is required).
  • Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

Edited by Rémy Coutable

Merge request reports

Loading