Update Homebrew formula to pull through Scarf endpoint #41
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the RisingWave Homebrew formula to fetch the RisingWave binary via a Scarf endpoint. This allows RisingWave maintainers to collect basic de-identified download and adoption metrics. It does not affect how previous versions of RisingWave are downloaded.
This change was suggested by the RisingWave product team in direct discussions. To test this, download RisingWave using the new endpoint (e.g. https://docker.risingwave.com/risingwave/archive/refs/tags/v1.9.1.tar.gz) and verify that the risingwavelabs/risingwave binary downloads without issue.
For future versions of RisingWave, the same formatting structure can be used without issue (with the version updated in the endpoint).