ci(release): stop leaking dist/wings_test into releases#7
Merged
Conversation
The release step globbed dist/*, which also picked up the committed dist/wings_test binary and attached it to every GitHub release as a stray 'wings_test' asset. Upload the two real build outputs explicitly so releases no longer leak that artifact.
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 release workflow uploaded
dist/*, which also attached the committeddist/wings_testbinary to every GitHub release as a straywings_testasset (had to be deleted manually on v1.13.0 and v1.13.1).Upload only the two real build outputs (
dist/wings_linux_amd64,dist/wings_linux_arm64) instead. No change to the committed binaries themselves.