Update Gitaly version

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.

changed milestone to %16.9

added Category:Gitaly automation:bot-authored groupgitaly maintenancedependency teamDelivery typemaintenance labels

assigned to @gitlab-release-tools-bot

added 1 commit

• d3407ca6 - Update gitaly to af2fbf3d304

Compare with previous version

added devopssystems group::gitalygit sectioncore platform labels

approved this merge request

enabled an automatic merge when the pipeline for 2a946e8c succeeds

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for d3407ca6

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 53     | 0      | 12      | 0     | 65    | ✅     |
| Plan        | 53     | 0      | 0       | 0     | 53    | ✅     |
| Govern      | 65     | 0      | 1       | 0     | 66    | ✅     |
| Package     | 24     | 0      | 2       | 0     | 26    | ✅     |
| Data Stores | 29     | 0      | 3       | 0     | 32    | ✅     |
| Verify      | 31     | 0      | 0       | 0     | 31    | ✅     |
| Monitor     | 7      | 0      | 0       | 0     | 7     | ✅     |
| Release     | 5      | 0      | 0       | 0     | 5     | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Manage      | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 269    | 0      | 19      | 0     | 288   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

merged

mentioned in commit b191519c

added teamDelivery workflowstaging-canary labels and removed teamDelivery label

added workflowcanary label and removed workflowstaging-canary label

added teamDelivery workflowstaging labels and removed teamDelivery workflowcanary labels

added teamDelivery workflowproduction labels and removed teamDelivery workflowstaging labels

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label