Deleting and reusing tag name causes reference to an older SHA of a tag
Summary
Creating a tag, and deleting it, and reusing the tag name causes go get
to reference the initial tag SHA, rather than the latest one.
Steps to reproduce
- Create a tag for a package that will be used by another package, in a format that is compatible with
go.mod
- Make noticeable changes to that package and commit changes
- Delete the tag, and recreate a tag with the same name, this time on the latest commit.
- Run
go get
in another package with<url>@<tag name>
- Verify which version of the tag the package is using
Example Project
What is the current bug behavior?
On pulling the tag using go get
, the old version with the initial SHA is used, rather than the newest one.
What is the expected correct behavior?
Since the tag with the old SHA was deleted, it should not persist on future references, and instead should be using the newest SHA for the newly created tag.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
Edited by Derek Phan