🛠 Fixed

• Download links from before 1.12.0 keep working: Installer packages were given versioned names in 1.12.0, which meant install scripts already deployed in your MDM no longer found a build under the name they were written for. Development, testing and acceptance builds are published under their familiar names again, alongside the new versioned names, so those scripts keep working unchanged. Production downloads were never affected.

App Catalog itself is identical to 1.12.0; this release only changes how installer packages are published.

Catalog App 1.12.0 introduces automatic self-updates, together with more reliable update detection and a round of security and stability fixes.

⚡ Improved

• App Catalog keeps itself up to date automatically, regardless of your update configuration, so it can never get stuck on an old version.

• Automatic updates now run by default when no update interval is configured. If you have never set UpdateInterval and do not want automatic updates, set it to 0 to opt out.

• More reliable version comparison. Apps with unusual version numbers (for example a build suffix in parentheses) are no longer incorrectly flagged as needing an update.

• Cleaner command-line output for administrators running App Catalog from the terminal.

🔧 Fixed

• Security hardening. Closed a local privilege-escalation path in the background agent and restricted its internal service to signed App Catalog components only.

• A transient network or backend issue no longer interrupts the scheduled update run.

• A missing version date, or a single problematic app, no longer stalls or aborts an update run.

• Removed a legacy version-reporting mechanism that could, in rare cases, freeze the background agent.

• App versions are now read without a private system API, improving long-term compatibility.

🛠 Fixed

• Macs could silently stop checking for updates: The update schedule was registered once during installation, and that registration could fail without reporting an error, most often when the package was installed while nobody was logged in. Nothing retried it, so the Mac never ran a scheduled update check again while continuing to look healthy in every other way. The schedule now ships as a regular background service inside the installer package, so installing and upgrading behave the same whether or not a user is logged in. Affected Macs recover automatically once they receive this version.

  • More information: Update schedule not found

• Permanent update prompt for apps without a version: Command line tools, uninstallers and anything that isn't an application bundle could show an update that never went away, because installing it couldn't change the outcome. These are now skipped, matching what the catalog command line tool already did.

• App locations matched imprecisely during scanning: Excluded locations are now matched on path components instead of as text, so a folder whose name merely begins with an excluded path is no longer skipped.

👀 Changed

• The command line tool leads with its subcommand syntax: The documentation, built-in help and generated deployment scripts now use the subcommand form, for example catalog install nl.root3.support. The familiar dash-style commands such as catalog --install keep working, so your existing scripts and MDM policies need no changes.

  • More information: Catalog Agent CLI