@leetickett-gitlab I bumped the Dockerfile and Gemfile in this MR to the new version but wasn't able to build the container because

[+] Building 0.4s (3/3) FINISHED
 => [internal] load local bake definitions                                                                                                                                                              0.0s
 => => reading from stdin 1.08kB                                                                                                                                                                        0.0s
 => [web internal] load build definition from dev.Dockerfile                                                                                                                                            0.0s
 => => transferring dockerfile: 795B                                                                                                                                                                    0.0s
 => ERROR [vite internal] load metadata for docker.io/library/ruby:4.0.2-bookworm                                                                                                                       0.2s
------
 > [vite internal] load metadata for docker.io/library/ruby:4.0.2-bookworm:
------
[+] build 0/2
 ⠙ Image contributors-gitlab-com-vite Building                                                                                                                                                          0.5s
 ⠙ Image contributors-gitlab-com-web  Building                                                                                                                                                          0.5s
dev.Dockerfile:1

--------------------

   1 | >>> FROM ruby:4.0.2-bookworm

   2 |     RUN curl -fsSL https://deb.nodesource.com/setup_24.x | bash -

   3 |     RUN echo "deb https://apt.postgresql.org/pub/repos/apt bookworm-pgdg main" > /etc/apt/sources.list.d/pgdg.list

--------------------

target vite: failed to solve: ruby:4.0.2-bookworm: failed to resolve source metadata for docker.io/library/ruby:4.0.2-bookworm: no match for platform in manifest: not found

I've confirmed that the tag exists: https://github.com/docker-library/ruby/blob/dbc0acf4dcb5f24c42dd4246d810c42e56be9163/4.0/bookworm/Dockerfile. I'm not sure what the issue is.

Arianna Haradon (c4222379) at 17 Mar 20:04

Closing as this was part of FY26-Q4 KRs.

Closing because the spike is over and we've begun implementation: #386

@leetickett-gitlab Unfortunately I don't remember. Is it documented somewhere? I dug up !1676 (merged) and !1655 (merged) which seem to be the last bump.

Arianna Haradon (408a0763) at 17 Mar 19:00

Implement codeowners which will make the contributors platform more secure by limiting those with merge rights.

/cc @gitlab-org/developer-relations/contributor-success

What does this MR do and why?

Add CODEOWNERS

Closes #382

/cc @leetickett-gitlab

Arianna Haradon (3ec25d80) at 17 Mar 19:00

... and 1 more commit

Arianna Haradon (f257930b) at 17 Mar 18:46

... and 48 more commits

@leetickett-gitlab are we ready for this?

@rutshah thanks for getting back to me. I'll post the issue on Discord and see if anyone wants to pick it up right now 🚀

@nick_vh could you please review and merge this MR? Thanks!

Why is this change being made?

To clarify quick win documentation

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
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• 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
  • Division: If the update affects your division, share the MR in your division 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
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update quick win language

Arianna Haradon (dc6b3936) at 17 Mar 17:00

What does this MR do and why?

Adds REST API endpoints for managing user mentorships, connecting the backend models introduced in !1875

Closes !1964

Validation steps

In rails console:

mentee = User.first
mentor = User.second

# CREATE
Mentorship.create!(mentor: mentor, mentee: mentee)

# INDEX 
mentee.mentee_mentorships.includes(:mentor).order(created_at: :asc).map { |m|
  { username: m.mentor.username, start_date: m.created_at }
}

# DESTROY
Mentorship.find_by(mentor: mentor, mentee: mentee).destroy!

# Confirm it's been deleted 
mentee.mentors.reload  # => []

/cc @leetickett-gitlab

LGTM

Arianna Haradon (01753851) at 16 Mar 17:57

... and 3 more commits