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.6

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

assigned to @gitlab-release-tools-bot

added devopssystems sectioncore platform labels

added 1 commit

• 6d87012c - Update gitaly to 4679a8713fc

Compare with previous version

approved this merge request

enabled an automatic merge when the pipeline for 3d8594b0 succeeds

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 6d87012c

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Create           | 40     | 0      | 6       | 0     | 46    | ✅     |
| Govern           | 46     | 0      | 2       | 0     | 48    | ✅     |
| Plan             | 55     | 0      | 0       | 0     | 55    | ✅     |
| Verify           | 20     | 0      | 0       | 0     | 20    | ✅     |
| Data Stores      | 22     | 0      | 0       | 0     | 22    | ✅     |
| Package          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Manage           | 0      | 0      | 1       | 0     | 1     | ➖     |
| Framework sanity | 0      | 0      | 1       | 0     | 1     | ➖     |
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 187    | 0      | 11      | 0     | 198   | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+

This merge request has been open for too long and will need manual intervention.

/cc @gl-gitaly

added auto updated label

requested review from @eread

approved this merge request

Hi @eread ,

GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.

This message was generated automatically. You're welcome to improve it.

added Technical Writing label

merged

mentioned in commit dd8308bc

added workflowstaging-canary 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