-
Notifications
You must be signed in to change notification settings - Fork 18k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/website/internal/dl: ?mode=json&include=all don't list older unstable releases when there are newer stable releases #37581
Comments
The This bug needs to be fixed. We should add test cases for this so this behavior doesn't regress.
Mind filing a separate GitHub issue for that? I'm not sure if we'll want to fix it because those versions are old, but in any case, it'll be easier to discuss and track it separately. |
Done: #37586 Thanks. |
Change https://golang.org/cl/290310 mentions this issue: |
Just to point out, per #43975, that every time this happens GitHub actions builds that are helpfully testing out new unstable versions stop working:
|
Just to reiterate the previous point that now Go 1.16 has been released all GitHub builds using rc1 have stopped working |
This is fixed. Old pre-release Go versions are now considered archived rather than not being included at all, and they show up both at the bottom of https://golang.org/dl/#archive and in the API with when Thanks for the report, and thanks to @seankhliao for investigating the problem and sending the fix CL. |
Updates golang/go#17574 Fixes golang/go#37581 Fixes golang/go#43975 Change-Id: I31cab4b8f8277b3c83ddde001f2649bb5f0bc9c7 Reviewed-on: https://go-review.googlesource.com/c/website/+/290310 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
The documentation at https://godoc.org/golang.org/x/website/internal/dl says that
However currently https://golang.org/dl/?mode=json&include=all does not include unstable releases.
Another issue is that for go < 1.6, the
SHA256
field is empty, but there is noSHA1
field that is instead present on the HTML page, in the archived versions section.The text was updated successfully, but these errors were encountered: