pale-moon 33.7.2 (new cask)

[synkathairo]

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

---

[synkathairo]

so it seems the test fails because I set the intel mac version to depend on lion or later (10.7)
(see https://www.palemoon.org/download.shtml)
should I set it to something later based on the latest macos version supported by homebrew?

[synkathairo]

macOS on ARM requires software to be signed. fails the macos-13, intel check? Is codesigning required for the intel version as well? If so, maybe the intel version should be removed from the cask? It seems like Pale Moon only signed the ARM version of the cask?

[synkathairo]

now edited to remove the Intel version which blocked checks (due to being unsigned)

[EricFromCanada]

Apparently the Intel builds are intentionally unsigned.