Question about Go Proxy and Incorrect Versions

Technical Discussion
1

Hello, I was testing a configuration change with Goreleaser and I ended up creating a new test tag and release on GitHub: v1.3.4

I deleted the release on GitHub after I was done checking the recent changes but I now noticed that pkg.go.dev has v1.3.4 listed on there but GitHub doesn’t anymore.

What happens in these scenarios now?

  1. I go to v1.4.0 and just continue from there? v1.3.4 doesn’t exist anymore on GitHub so I am not sure what the consequences are for that. The Golang Proxy will now always have v1.3.4 which is a little annoying. I guess this wouldn’t affect using go install user/repo@latest.
  2. I release another v1.3.4 but make it an actual release that I would keep but it would not match the original v1.3.4 from earlier in the Golang Proxy. Plus, the date would not match.

Here are links to both the GitHub and the Proxy modules

1 Like
2

The Go module proxy considers tags to be immutable. Consequently, re-pushing v1.3.4 for a different commit won’t work.

You will need to release v1.3.5 (or v1.4.0) instead. And it is suggested to include a retract directive in your go.mod for the unintended v1.3.4 release. Go Modules Reference - The Go Programming Language

1 Like
3

Alright, thanks for the input. I’ll go ahead and release v1.4.0 instead.