The macOS DMG previously included in the v2.2.0 release has been removed because it is not usable for normal users.
After downloading the DMG, moving LASSIE to Applications, and opening it, macOS reports that lassie.app is damaged. The file itself is not corrupted; the app is only ad-hoc signed and has not been notarized by Apple, so Gatekeeper rejects it.
To publish a working macOS release, the app and DMG must be signed with an Apple Developer ID Application certificate and notarized by Apple.
This requires access to an Apple Developer Program account. We may need to contact the University of Illinois, department IT, or another appropriate campus office to use an institution-managed Apple Developer account or signing service and securely configure the required GitHub Actions credentials.
Until Developer ID signing and notarization are available, a macOS DMG should not be included in GitHub Releases.
The macOS DMG previously included in the v2.2.0 release has been removed because it is not usable for normal users.
After downloading the DMG, moving LASSIE to Applications, and opening it, macOS reports that
lassie.appis damaged. The file itself is not corrupted; the app is only ad-hoc signed and has not been notarized by Apple, so Gatekeeper rejects it.To publish a working macOS release, the app and DMG must be signed with an Apple Developer ID Application certificate and notarized by Apple.
This requires access to an Apple Developer Program account. We may need to contact the University of Illinois, department IT, or another appropriate campus office to use an institution-managed Apple Developer account or signing service and securely configure the required GitHub Actions credentials.
Until Developer ID signing and notarization are available, a macOS DMG should not be included in GitHub Releases.