fix: use .tar.gz for all distributables#144
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.
Fixes #143
Root cause: The npm package
goBinary.urltemplate expects.tar.gzfiles for all platforms, but Windows releases were packaged as.zipfiles, causing the download to fail with a 404 error.Note that
go-npm-nexthas always useduntar.Solution
Changed Windows archive format from
.zipto.tar.gzby removing theformat_overridessection in.goreleaser/windows.yml. This creates consistency across all platforms and aligns with the npm package expectations.Benefits
.tar.gzformat.tar.gzTesting
.tar.gzarchivesgo-npm-nextextractionFiles Changed
.goreleaser/windows.yml- Removed Windows-specific.zipformat override