Skip to content

feat: add Icon Composer #223157

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

martimlobao
Copy link
Contributor

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 (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.

Unsure if this counts as beta software and should therefore not be included here. Also not sure I caught everything for the zap stanza.

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.

Here's a working livecheck

  livecheck do
    url :url
    strategy :extract_plist do |items|
      items["com.apple.IconComposer"]&.short_version
    end
  end

- Apple app to create Liquid Glass icons
- see: https://developer.apple.com/icon-composer/
@bevanjkay bevanjkay force-pushed the feat/add-icon-composer branch from 6ddae5a to a1988cd Compare August 9, 2025 09:55
@bevanjkay
Copy link
Member

The audit failure here is a "false positive" - Apple has a special case for their own software that doesn't require the same codesigning steps as any others.

@martimlobao
Copy link
Contributor Author

The audit failure here is a "false positive" - Apple has a special case for their own software that doesn't require the same codesigning steps as any others.

Yeah, I figured it was either that or something to do with this being in beta and perhaps only working on macOS 26 (haven't tested on older macOS versions).

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.

3 participants