Releases: jamf/Notifier
Releases · jamf/Notifier
Notifier
Notifier
- Completely rewritten and linted with SwiftLint
- Removed NSUserNotifications Framework calls
- Now requires macOS 10.15+
- The .app is now 10 x smaller at (4.2MB vs 42MB) and the PKG is 7.5 x smaller (1.8MB vs 12.5MB)
- Can now be rebranded via the
--rebrand
flag - PKG corrected to not be relocatable
- Corrected an issue where Notifier.app would hang if passed a valid type only (
--type alert
or--type banner
) - Can now be notarised (#21 and #22)
- Support has been added to
--messageaction
and--messagebuttonaction
so that, passing 'logout' will prompt the user to logout, if passed a single item, this will be launched via:/usr/bin/open
, more complex commands can be passed, but the 1st argument needs to be a binaries path (for example/usr/bin/open
will work,open
will not) ((#8 and #23)
What's Changed
Full Changelog: 2.3...3.0
Notifier
Addresses the following:
#1 - Move to ArgumentParser - but now minimum OS is 10.13.
#17 - Swift Compile Error
Additionally, v3 will be out in the next few months. This will require macOS 10.15+ and as such will drop support for the NSUserNotifications API.
But will allow us to address some of the outstanding issues.
What's Changed
- Add additional note for Signing by @Chalcahuite in #13
- Argument parser migration by @macmule in #20
New Contributors
- @Chalcahuite made their first contribution in #13
Full Changelog: 2.2.3...2.3
Notifier
Addresses #9:
com.apple.notificationcenterui2
has been the bundle ID of Notification Centre up to BS B9.. now it’scom.apple.notificationcenteru
, which is the same as any macOS before.So can revert the changes for this and the issue with the
if #available
API and BS is now moot as not needed for BS checking anymore.
As such, Big Sur b9+ supported