Do not use redirects for latest binaries #157
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is |
rail
force-pushed
the
no-more-redirects
branch
2 times, most recently
from
f30220a to
f18353b
Compare
After we moved the edge CDN to GCS-backed Google CDN, the latest binaries became actual binaries, without redirects, as it was before. This PR removes the redirect resolution logic.
rail
force-pushed
the
no-more-redirects
branch
from
f18353b to
4c999fd
Compare
rafiss
approved these changes
Dec 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After we moved the edge CDN to GCS-backed Google CDN, the latest binaries became actual binaries, without redirects, as it was before.
This PR removes the redirect resolution logic.
I also pinned clrfmt to the version that doesn't use generics and added go-1.19 to the test matrix.