You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discovered in restic/restic#5154 the official go mod proxy returns a slightly different repository content (just an extra CHANGELOG.md) compared to what is currently referenced by tag v0.6.1.
The tag currently points at e00c584, but based on a comparison with the data cached at the go mod proxy it was original created from efa10c0 . Judging from the contained changelog, the latter commit is also the one that was intended to be tagged as v0.6.1.
Is there a reason why the tag was moved? And can it be returned to the original commit?
The text was updated successfully, but these errors were encountered:
As discovered in restic/restic#5154 the official go mod proxy returns a slightly different repository content (just an extra
CHANGELOG.md
) compared to what is currently referenced by tag v0.6.1.The tag currently points at e00c584, but based on a comparison with the data cached at the go mod proxy it was original created from efa10c0 . Judging from the contained changelog, the latter commit is also the one that was intended to be tagged as v0.6.1.
Is there a reason why the tag was moved? And can it be returned to the original commit?
The text was updated successfully, but these errors were encountered: