fix: use Go module proxy instead of GitHub API to resolve client version#207
Open
fix: use Go module proxy instead of GitHub API to resolve client version#207
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
resolve-latestaction used an unauthenticated GitHub API call to resolve the latest client version. This is unreliable because:curl --silentsuppresses the error andjqreturns the literal stringnullgo install ...@nullwhich fails with "invalid version: unknown revision null"This has caused flaky conformance test failures in downstream
functions-framework-*repos.Replace with
go list -mwhich resolves the version through Go's module proxy (proxy.golang.org). This is more reliable (no rate limiting) and purpose-built for version resolution.Also fixes deprecated
::set-outputsyntax in favor of$GITHUB_OUTPUT.