Repository navigation
chore(pulse): replace deprecated archive format keys in goreleaser - #44
Merged
Merged
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
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.
Description
goreleaser checkfailed because the archive settings used the deprecated keysarchives.formatandarchives.format_overrides.format. They now useformats, which takes a list:[tar.gz]by default and[zip]for Windows. The release files stay the same.With GoReleaser 2.20.0,
goreleaser checkpasses. A snapshot release (goreleaser release --snapshot --clean --skip=publish) on a copy of the branch made the same files as before: tar.gz archives for Linux and macOS, zip archives for Windows, andchecksums.txt. Each archive holds the three demos,README.mdandLICENSE.Issues
None.
Type of Change
Checklist
gofmt,go vet).go test -race ./...) and everything builds (go build ./...andgo -C examples build ./...).