Requirements

S.U.P.E.R.M.A.N. (or just super) enforces macOS updates and upgrades via multiple workflows that vary based on the system's current macOS version and CPU architecture. At this time super does not support Mac App Store updates or Studio Display Firmware Updates.

Mac Computers With Intel

macOS 11 or newer.
The super script must run with system (root) privileges, but no additional credentials or MDM service is required.

Mac Computers With Apple Silicon

The super script must run with system (root) privileges.
To enforce automatic macOS updates or upgrades via local authentication requires providing super with the local credentials of an existing account.
To enforce automatic macOS updates or upgrades via Jamf Pro MDM requires macOS 11.5 or newer, Jamf Pro 10.35 or newer, and providing super with Jamf Pro API credentials.

If no credentials are provided to`super` then macOS updates and upgrades can not be enforced on Mac computers with Apple silicon. In this case `super` prompts the user to provide their local account password.

Apple silicon user authentication dialog

User authentication dialog

Updating & Upgrading `super` Itself

New versions of super can always be installed on top of older versions. However, a major version upgrade (like 3.0 to 4.x) of super indicates significant configuration changes such that settings for an older version of super are not compatible. If you have a working configuration for super version 3.0 you can upgrade your settings to support super version 4.x. There is no upgrade path for versions of super prior to version 3.0.

Previously saved super 3.0 Apple silicon authentication credentials are automatically migrated the first time super 4.x runs.
Refer to this spreadsheet (tab separated values) for migrating super 3.0 command line options to version 4.x.
Refer to this spreadsheet (tab separated values) for migrating super 3.0 managed preferences to version 4.x.
It is safe to mix super version 3.0 and 4.x managed preferences (except for the DisplaySilently setting) in a single configuration profile. However, each version only recognizes the managed preference keys that are compatible for that version.
Updated example MDM configuration profiles for super v4.x.
The latest Jamf Pro Extension Attribute scripts supports both super versions 3.0 and 4.x.