1

I am looking at the contents of the GOPROXY cache. We publish a module https://github.com/google/oss-rebuild/. We don't have any tagged releases yet but we do have pseudo versions. For example, v0.0.0-20251008203231-2e9e242ca650. As of the date of this post, I can find this out using https://proxy.golang.org/github.com/google/oss-rebuild/@latest.

enter image description here

Note that pseudo versions are not mentioned on https://proxy.golang.org/github.com/google/oss-rebuild/@v/list because "the go command considered pseudo-versions in $base/$module/@v/list to be pre-release versions, but this is no longer true since Go 1.13.".

Now, the documentation says that we can find the zip file using $module/@v/$version.zip. So this would mean that the URL for this request would be: https://proxy.golang.org/github.com/google/oss-rebuild/@latest/v0.0.0-20251008203231-2e9e242ca650.zip. However, this returns an error bad request: missing /@v/. Am I constructing the URL wrong here? I have tried different permutations like: https://proxy.golang.org/github.com/google/oss-rebuild/@v0.0.0-20251008203231-2e9e242ca650.zip, but I still get the same error.

Improve this question

1 Answer 1

Reset to default
1

It seems the correct URL is https://proxy.golang.org/github.com/google/oss-rebuild/@v/v0.0.0-20251008203231-2e9e242ca650.zip (replace @latest with @v).

This proves that GOPROXY does cache untagged commits too.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.