This repository has been archived by the owner on May 2, 2024. It is now read-only.
utm-beta: add livecheck #14946
Merged
utm-beta: add livecheck #14946
Conversation
This file contains 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
samford
added
ci-syntax-only
bevanjkay
approved these changes
Oct 25, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.
In the following questions
<cask>is the token of the cask you're submitting.After making all changes to a cask, verify:
brew audit --cask --online <cask>is error-free.brew style --fix <cask>reports no offenses.Additionally, if adding a new cask:
brew audit --new-cask <cask>worked successfully.brew install --cask <cask>worked successfully.brew uninstall --cask <cask>worked successfully.By default, livecheck checks the Git tags for
utm-betaand this currently gives a stable version as newest (4.0.8). We discussed this in #14917 and it seemed reasonable to restrict this to unstable versions (e.g., beta, RC, RC2, etc.).This PR adds a
livecheckblock that restricts matching to releases that are marked as "prerelease" on GitHub. At the moment, this is the easiest way to avoid stable versions in that particular repository (so long as they continue to be diligent about marking releases as "prerelease").