jockoshop 0.1.14

Supersedes 0.1.12 and 0.1.13, which both lost their macOS builds while macOS signing was being set up.

macOS builds are back, and signed

Signed with a Developer ID certificate, not yet notarized. macOS still warns on first launch — right-click jockoshop.app → Open — because notarization is what removes that and nothing else does.

Verified on the built bundle rather than assumed: the authority chain runs to Apple Root CA, the hardened runtime flag is set, and codesign reports it valid on disk and satisfying its designated requirement. Gatekeeper rejects it for exactly one reason, Unnotarized Developer ID — so the certificate side is right and only notarization is outstanding.

Apple rejects the notarization credentials with a 401, so that step is parked rather than blocking releases. Since notarizing runs after signing, a failure there does not leave an unnotarized build, it loses the macOS builds altogether — which is what happened twice.

Windows and Linux builds are unsigned — SmartScreen shows "More info" → "Run anyway".

From 0.1.12

The top-left is now the app's own icon rather than the word "jockoshop". Clicking it opens an About box with the version, the commit it was built from, and links to the repository and the release builds.

Still unverified

The FTP upload from 0.1.10 has never touched a real server — tested end-to-end against a mock board speaking Synchronet's dialect, but no live BBS.