Repository navigation
ci: update the Homebrew tap on each release - #124
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
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.
Adds a
homebrew-tapjob to the release workflow that bumpsversionandsha256in MegaManSec/homebrew-tap after each release. It pushes with a write deploy key scoped to the tap repo, stored asHOMEBREW_TAP_DEPLOY_KEYin thehomebrew-tapenvironment (deployable frommainonly).Before updating, the job checks the published
app.zipwithgh attestation verifyagainst this repo'srelease.ymlonmain, and skips if the tap is already at the same or a newer version.README: Homebrew install instructions under Installation, and an author line under Support.
Refs #123