Skip to content
Snippets Groups Projects

Update Gitaly version

Merged GitLab Release Tools Bot requested to merge release-tools/update-gitaly into master

Update Gitaly to the latest green master

What should I do if this pipeline is red?

  • Look at the failure. If it looks unrelated to Gitaly, it's likely a master:broken or failureflaky-test.
    1. Open the Pipelines tab and click Run Pipeline.
    2. This will run a pipeline for merge result.
  • If it looks related to Gitaly, notify the Gitaly team in #g_gitaly on Slack.

What should I do in case of merge conflicts?

If someone updates GITALY_SERVER_VERSION with another MR, we may have a merge conflict.

In such unlikely circumstances, the better option will be closing this merge request and deleting the release-tools/update-gitaly branch.

release-tools will take care of creating a new merge request in about 1 hour.


🤖 This merge request was generated via release-tools pipeline.

Do you want to improve this message? You can find it here! teamDelivery loves merge requests.

Merge request reports

Merged results pipeline #1155503484 passed

Pipeline: E2E GDK

#1155508441

    Pipeline: GitLab

    #1155507944

      Merged results pipeline passed for 1e71b184

      Test coverage 81.64% (16.80%) from 2 jobs

      Merged by avatar (Mar 30, 2025 7:32pm UTC)

      Loading

      Pipeline #1156293817 passed

      Pipeline passed for 05e76336 on master

      Test coverage 64.83% (16.80%) from 2 jobs
      10 environments impacted.

      Activity

      Filter activity
      • Approvals
      • Assignees & reviewers
      • Comments (from bots)
      • Comments (from users)
      • Commits & branches
      • Edits
      • Labels
      • Lock status
      • Mentions
      • Merge request status
      • Tracking
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      • Loading
      Please register or sign in to reply
      Loading