wsjt-x 2.7.0 (new cask)

[jaredledvina]

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.

---

Currently the app is unsigned and fails the audit:

audit for wsjt-x: failed
 - Signature verification failed:
/private/tmp/cask-audit20250424-87117-7cuztu/wsjtx.app: rejected

macOS on ARM requires software to be signed.
Please contact the upstream developer to let them know they should sign and notarize their software.
wsjt-x
  * line 5, col 2: Signature verification failed:
    /private/tmp/cask-audit20250424-87117-7cuztu/wsjtx.app: rejected

    macOS on ARM requires software to be signed.
    Please contact the upstream developer to let them know they should sign and notarize their software.
Error: 1 problem in 1 cask detected.

I've emailed the developers list to ask about plans to notarize & sign the app.

[krehel]

Hey @jaredledvina - thanks for opening this PR! I'm going to close it for now, pending any updates from upstream regarding signing.

If/when the app is signed, please feel free to resubmit the PR.

If the decision from upstream is to not sign, you can always host the application in your own tap