Repository navigation
Describe the tap's automated cask bump in the release docs - #4
Merged
Merged
Conversation
The homebrew-tap now runs a daily Bump workflow that opens a PR with the cask's new version and sha256 after each release, so the instructions to bump the cask by hand are out of date. Say that the PR arrives within a day and only needs reviewing and merging.
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.
Criseda/homebrew-tap now has a daily Bump workflow (
.github/workflows/bump.yml) that runs livecheck and opens a PR when there is a newer app release. The header of.github/workflows/release.ymland the Homebrew bullet in AGENTS.md still said to bump the cask'sversionandsha256by hand; they now say the tap's PR arrives within a day and you review and merge it.Docs only, not user-facing, so no CHANGELOG entry.