Drop 386 release targets from GoReleaser builds - #92
Merged
Merged
Conversation
Restrict release builds to amd64 and arm64 on linux, windows, and darwin (six archives instead of eight). GoReleaser's default arch list includes 386, so 32-bit archives were published implicitly. Download counts across all releases show one download per 386 asset at most, consistent with automated fetchers rather than users, while the 32-bit targets add build and CI surface for dependencies that are 64-bit oriented (the planned embedded Graphviz renderer runs on wazero, which has no optimizing compiler on 386). The archive name template no longer needs the i386 special case. Verified with `goreleaser check` and `goreleaser build --snapshot`, which produced exactly the six expected targets.
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.
Summary
Restrict GoReleaser builds to
amd64andarm64on linux, windows, and darwin. Release archives go from eight to six; thei386special case in the archive name template is removed.Why
goarchlist includes386, so 32-bit archives were published implicitly, never by decision.gh api repos/apstndb/execspansql/releases): 386 assets total 4 downloads, exactly one per Linux/Windows i386 asset on v0.4.0 and v0.5.0-alpha.3 and zero elsewhere, which matches automated fetchers rather than users. amd64 and arm64 totals are 7 and 6.Verification
goreleaser check: configuration valid.goreleaser build --snapshot --clean --skip=validate: built exactlylinux_amd64,linux_arm64,windows_amd64,windows_arm64,darwin_amd64,darwin_arm64.Release note
Breaking for anyone consuming the
*_i386.*release assets: 32-bit builds are discontinued starting with the next release.go installon 386 hosts is unaffected.