Repository navigation
[CI] Skip the Go build cache in the Publish job - #2
Merged
Merged
Conversation
The Publish job sets up Go without checking out the repository, so setup-go's cache step warned on every run that it found no go.mod. The job only runs `go list -m` against the proxy and has nothing to cache. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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 Publish job of the Release workflow sets up Go without checking out the repository, so setup-go's cache step warned on the v1.4.4 release run that it found no go.mod to key a cache on. The job only runs
go list -magainst the module proxy and has nothing to cache, so the cache is turned off there. The push triggers the workflow's dry run as usual.🤖 Generated with Claude Code