What you see seems to be triggered by having the old version in the module cache and not being able to download the new version.

Things you can try to diagnose the problem:

1. Is it a private module?

Check GOPRIVATE.

2. Can you access the module from the CI system?

Try git ls-remote https://gitlab.com/my-proj/common.git, also with git\+ssh:// and ssh://

3. Does it happen every time with empty module cache?

Try go clean -modcache. Caution: This slows down compile times.

Considering your replace directive: You don't replace something for version independence, instead you specify a different module name.

Every gitlab.com/my-proj/common version is replaced by gitlab.com/my-proj/common.git (note the appended .git in the name) version v0.2.29.

This is a work around for GitLab for packages that are in subgroup, I would suggest following the official documentation in “Use a project as a Go package” and authenticate Go requests instead.

As described in the documentation you are following to install on the first paragraph:

You can download a binary for every available version as described in Bleeding Edge - download any other tagged release.

Following the link in this sentence allow your to find the tag list page

Last version in 1.X (Hence compatible with 8.X versions of Gitlab is 1.11.2 at time of writing, you can download it from The tag details page

If you prefer another archive format, you can choose in the dropdown of download at the right of the tag page description:

As stated in the release note of GitLab 9 runners above version 9 use the new v4 API and requires at least Gitlab 9.0.

So any runner version below 9 should do it.

Tip: Keep the version of your GitLab instance always above your runners to avoid any problem.

To downgrade your runner:

1. Uninstall it;

2. Download the desired package from this repo;

3. Install the package.