Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issie 4.1.3 (new cask) #170773

Closed
wants to merge 1 commit into from
Closed

issie 4.1.3 (new cask) #170773

wants to merge 1 commit into from

Conversation

0x6770
Copy link

@0x6770 0x6770 commented Apr 6, 2024

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:

Additionally, if adding a new cask:

  • Named the cask according to the token reference.
  • Checked the cask was not already refused.
  • Checked the cask is submitted to the correct repo.
  • 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. and removed missing zap Cask is missing a zap stanza, please add one. labels Apr 6, 2024
@0x6770 0x6770 changed the title issie 4.1.3 issie 4.1.3 (new cask) Apr 6, 2024
@razvanazamfirei
Copy link
Contributor

Thank you for your submission @0x6770, but we cannot accept it at this time because it does not pass our signature verification check that are a requirement for new submissions:

macOS on ARM requires applications to be signed. Please contact the upstream developer to let them know they should notarize their package.

Please consider hosting this in your own Tap and if the developers sign their app in the future we would then be happy to consider adding this to homebrew-cask.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants