Repository navigation
fix: key the linux tarball upload on the tarball - #17
Merged
Merged
Conversation
hyperi-ci's release tail writes <tag>/macbash-linux-<arch>.sha256 for the raw binary before Package runs. The linux tarball job used that same file as its write-once marker, so on the next release it would have found it, skipped, and never published the linux tarballs or the tarball line the Homebrew formula reads. The marker is now the tarball, which only this job writes, and it goes up after the .sha256.
|
Released in v1.5.12 -- https://github.com/hyperi-io/macbash/releases/tag/v1.5.12 |
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.
Follow-up to #16. As merged, the next release would have published no linux tarballs.
<tag>/macbash-linux-<arch>.sha256for the raw binary. fix: refuse unverified installs and fork publishes #16 used that same file as the linux tarball job's write-once marker, so the job would find it and skip, and the tarball line the Homebrew formula pins would never land..sha256.docs/release.mdnames the marker each upload checks.