Skip to content

Conversation

@zied-elouaer
Copy link

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 any changes to a cask, existing or new, verify:

  • The submission is for a stable version or documented exception. (No stable version exists yet. This is for a Beta release which accepted according to the documented exceptions)
  • brew audit --cask --online <cask> is error-free.
  • brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

  • Named the cask according to the token reference.
  • Checked the cask was not already refused (add your cask's name to the end of the search field).
  • brew audit --cask --new <cask> worked successfully.
  • HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
  • brew uninstall --cask <cask> worked successfully.

@BrewTestBot BrewTestBot added new cask missing zap Cask is missing a zap stanza, please add one. labels Dec 22, 2025
Copy link
Member

@bevanjkay bevanjkay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please try to add a zap stanza. The linked documentation provides some recommended methods to create it.

@krehel
Copy link
Member

krehel commented Dec 23, 2025

This software does not appear to be generally available to everyone?

terramate catalyst

@zied-elouaer
Copy link
Author

This software does not appear to be generally available to everyone?

terramate catalyst

It is generally available now. We will update the README to reflect that. Thanks.

@zied-elouaer zied-elouaer force-pushed the add-terramate-catalyst branch from 9a4da12 to cd1c568 Compare December 24, 2025 17:13
@BrewTestBot BrewTestBot removed the missing zap Cask is missing a zap stanza, please add one. label Dec 24, 2025
@zied-elouaer
Copy link
Author

Please try to add a zap stanza. The linked documentation provides some recommended methods to create it.

Done.

Please also note that I tried adding a conflicts_with since this installs the same binary name as the terramate formula but it seems Casks only support other Casks as a conflict.

Please let me know if any other changes are required to accept this PR. Thanks.

@zied-elouaer zied-elouaer force-pushed the add-terramate-catalyst branch from cd1c568 to 6235985 Compare December 24, 2025 17:19
@soerenmartius
Copy link

soerenmartius commented Jan 10, 2026

@krehel @bevanjkay any chance to move this forward pls?

@bevanjkay
Copy link
Member

@soerenmartius The notability issue is still a concern, in cases where a repository is only used for releases this can be waived, but in order for this to take place we need a publicly accessible webpage that refers to the product. The cask doesn't currently provide anything other than the repository.

There are also a couple of other issues causing brew audit to fail - despite the PR description checkbox indicating that everything that they were passing.

If assistance is required feel free to reach out and ask for help with any of the specific issues, but note that Homebrew maintainers are unable to push directly to this PR because it has been opened from an organisation-owned fork.

homepage "https://github.com/terramate-io/terramate-catalyst"

livecheck do
url "https://github.com/terramate-io/terramate-catalyst/releases"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
url "https://github.com/terramate-io/terramate-catalyst/releases"
url :url

For some reason the repository is unable to be fetched using the GitHub api, which is causing brew livecheck to fail. I'm not sure if repository settings can cause this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants