Skip to content

Add a fix to the 16.9.2 patch release post

Michael Kozono requested to merge mkozono-master-patch-1d3c into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

gitlab-org/gitlab!145036 (merged) was included in 16.9.2 https://gitlab.slack.com/archives/CB2S7NNDP/p1709922302406419:

image

So this MR adds it to the release post.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • [-] For transparency, share this MR with the audience that will be impacted.
    • [-] Team: For changes that affect your direct team, share in your group Slack channel
    • [-] Department: If the update affects your department, share the MR in your department Slack channel
    • [-] Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Merge request reports