diff options
| author | Stan Hu <stanhu@gmail.com> | 2020-09-30 23:58:34 -0700 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2020-10-01 07:12:24 -0700 |
| commit | 2743dfba8b9e4727ee6df79caf427852b005cf99 (patch) | |
| tree | 3afa46980d1702b87dcaa8d139ee0b573cc4f4c6 /internal/command/command.go | |
| parent | 1a2bfecd2f0ebb8e31f9833e0522c4643797041b (diff) | |
| download | gitlab-shell-2743dfba8b9e4727ee6df79caf427852b005cf99.tar.gz | |
Update Gitaly module dependencysh-update-gitaly-dep
This updates Gitaly's latest Protocol Buffer definitions, which were
last updated in Feburary 2020, with the latest version of Gitaly. This
is done to ensure the definitions are in sync with Workhorse
(https://gitlab.com/gitlab-org/gitlab-workhorse/-/merge_requests/619)
and Gitaly.
Because we started tagging Gitaly versions `v13.x.x` instead of
`v1.x.x`, `go get` refuses to update the Gitaly module using the latest
tag or SHA (https://gitlab.com/gitlab-org/gitaly/-/issues/3177). Go
tries to enforce semantic compatibility by requiring the use of module
paths (e.g. `m/v13`), and Gitaly doesn't adhere to this scheme.
To workaround this issue, we use the replace directive
(https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive):
```
go mod edit -replace gitlab.com/gitlab-org/gitaly=gitlab.com/gitlab-org/gitaly@3f5e218def93024f3aafe590c22cd1b29f744105
```
Diffstat (limited to 'internal/command/command.go')
0 files changed, 0 insertions, 0 deletions