Support gomod configuration in goreleaser #391
Merged
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.
goreleaser added support for a
gomod.proxyconfiguration stanza in v0.162.0The docs indicate --snapshot will ignore the setting so the flag is replaced with the implied
--skip-publish --skip-validate --skip-announce.I looked into adding an explicit proxy config into .goreleaser.yaml, but it appears the goreleaser cli doesn't allow for dynamic overrides. --config is repeatable, but the second file replaces the config instead of merging.
make bootstrap buildshould behave the same, but these changes allow for:`
make bootstrap
echo "gomod:
proxy: true
env:
make build
`
Signed-off-by: Conor Nosal [email protected]