Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
Fresh off the release of macOS Sierra, we've got a new version of AutoPkgr that includes some important fixes for 10.12 compatibility. We've also added amazingly easy one-click integration with the great new VirusTotalAnalyzer processor from Hannes Juutilainen, which checks downloaded files against the VirusTotal database.
Important note: this version of AutoPkgr no longer supports OS X Mountain Lion (10.8).
- Updated versions of MMMarkdown and MailCore2 used in AutoPkgr.
- Clarified wording on the selective notifications picker (thanks to @poundbangbash for the wordsmithing).
- Prepared for localization, starting with French. (#537, big thanks to Guillaume Gete)
- Left-aligned results of recipe searches.
- Updated hard-coded default list of AutoPkg repos used when GitHub is not accessible.
- Fixed issues with storing notification credentials in the AutoPkgr keychain in macOS Sierra. (#554, #555)
- Fixed the AutoPkgr Slack bot icon URL. (#527)
- Fixed a bug that would prevent notifications from being sent if the notification trigger actions were never customized. (#533)
- Fixed a bug that caused the width of the AutoPkgr window to snap back to defaults when clicking on the Notifications tab. (#499)
- Some typos found and corrected.
- Removed 10.8 support. AutoPkgr now requires Mac OS X 10.9 or higher.
Version 1.4.1 of AutoPkgr is now available, and it has a larger-than-your-average-point-release number of improvements and changes. Take a look:
- AutoPkgr now allows you to customize the template used to generate notifications when new actions have occurred. Check it out at the bottom of the Notifications tab. (#184)
- Fixed a long-standing issue that caused an incorrect prompt for the AutoPkgr keychain password! (#469)
- Addressed several issues that may have prevented notifications from working reliably in version 1.4. (#508, #515)
- Fixed a crash caused by the SMTP server setting being blank. (#502)
- AutoPkgr launches a bit faster now. (#500)
- AutoPkgr now reports InstallFromDMG processor results in addition to Installer processor results.
- Fixed an issue that would cause the email notification subject to be blank.
- Adjusted default formatting of email and Slack notifications. (#507)
- Added logging for SMTP operations.
- Prevented password field from wrapping to a "new line." (#481)
- Increased width of active recipe list picker.
- Updated versions of MMMarkdown and MailCore2 used in AutoPkgr.
A note on keychain security in AutoPkgr 1.4.1:
The fix for issue #469 requires AutoPkgr to be less aggressive when locking the AutoPkgr keychain (a separate keychain stored in ~/Library/Keychains that stores your SMTP credentials for email notifications). It's possible for somebody with access to your AutoPkgr Mac to obtain your SMTP password using the
securitycommand while the AutoPkgr keychain is unlocked.
Here's why AutoPkgr exceeds our security requirements, even with less aggressive keychain locking:
- AutoPkgr's locking behavior is still more restrictive than your login keychain's behavior.
- Physical access or VNC to your AutoPkgr Mac is necessary to use the
securitycommand to obtain the SMTP password.
- AutoPkgr goes to great lengths to keep the actual AutoPkgr keychain password both unknown and unnecessary to know, which prevents password exposure via the Keychain Access app.
Taking common sense security steps should mitigate any risks introduced by this change. Here are three to consider:
- Use an SMTP account dedicated to AutoPkgr for email notifications.
- Run AutoPkgr on a dedicated Mac or VM, rather than using one shared by other services.
- Unless necessary, don't leave the Mac logged in. AutoPkgr works great at the login window (which is why it has its own keychain in the first place), and a Mac at the login window is magnitudes safer than one with an active user session.
There's a little something for everybody in this major AutoPkgr release! We especially think you'll love the ability to mute certain types of notifications, the new simplified JSSImporter interface (with CDP support), and the much-requested ability to add/remove repos and recipes in bulk using multi-selection.
As always, get in touch with us if you have questions! Questions are welcome in our Google Group, and if you find a reproducible problem, please submit an issue on GitHub. The #autopkg channel on the MacAdmins Slack team is also an excellent place to get real-time support for AutoPkg and AutoPkgr.
We hope you love it!
- You can now select which events trigger a notification. For example, you can receive only Munki import notifications, and ignore download notifications. In other words, no more daily emails about VLC downloading! (#184)
- Ability to select multiple repos and then update, add, or remove the selected repos. (#434)
- Ability to select multiple recipes and then run, enable, or disable the selected recipes. (#434)
- Built-in integration with FileWave version 10 and higher, via the new FileWaveImporter processor. (#339, with thanks to @johncclayton.)
- Integration with new LANrevImporter processor. (#488) See the LANrevImporter wiki for information on migrating from AbsoluteManageExport.
- Ability to switch between multiple recipe lists. (#263)
- Ability to specify pre/post processors. (#346, #384)
- MakeCatalogs.munki will be included when .munki recipes are run from the contextual menu. (#485)
- Fixed a bug that caused progress spinners to incorrectly display on multiple recipes if they share the same name. (#447)
- Fixed a bug that caused AutoPkgr to freeze when adding a custom repo with a trailing space in the URL. (#486)
- Fixed a minor counting error in log output. (#446)
- Fixed crash that occurred if Git was not reinstalled after an OS X upgrade. (#458)
- Fixed a bug that resulted in unreliable "Run This Only Recipe Only" selection. (#456)
- XPC connections to helper tool are now explicitly closed on process completion.
- Totally redesigned and simplified the JSSImporter settings sheet.
- JSSImporter configuration UI now supports cloud distribution points (CDP) and local distribution points. (#463, #309)
- MakeCatalogs.munki recipe is now added by name rather than by identifier. An override with the same name will now be used, if one exists. (Hat tip to @grahampugh.)
- General improvements to integration performance. No longer makes duplicate GitHub API calls when "releases" don't exist.
- Updated "AutoPkgr" link in footer of notification emails to point to AutoPkgr information page instead of GitHub repo.
- Moved Recipe/Override chooser out of contextual menu and into AutoPkg preference panel.
- Widened images in readme.md so they'll look awesome with GitHub.com's new repo layout.
- Updated bundled version of Sparkle auto-update framework.
- The "Add Repo" button and associated text field now work with any supported URL, not just HTTPS.
- When you right-click and run a single Munki recipe, AutoPkgr will now run MakeCatalogs.munki too.
- Made width of tab views more consistent.
AutoPkgr 1.3.2 is now available, and fixes a couple bugs that were reported by the community.
- You can now specify the name of the AutoPkgr bot when configuring Slack integration. (#437)
- Now includes localized hostname in all notifications, not just email.
- Fixed an unpleasant freeze that occurred after installing JSSImporter. (#443)
- AutoPkgr now more gracefully handles mid-run interactive prompts from AutoPkg, which is usually a result of missing parent recipes. (#441)
- Fixed a bug that resulted in errors when a repo path contained spaces. (#435)
- Fixed a tiny typo in the default Munki repo path.
- Resolved an issue in the CocoaPods configuration.
If you have any trouble with AutoPkgr, first check the Troubleshooting section of the README file. We've tried to describe a few common solutions to problems there.
Still have questions after reading the manual? Reach out to us on the MacAdmins Slack channel, or on the AutoPkgr discussion group. Or if you believe you've discovered a reproducible bug, please submit an issue on GitHub.
We've started collecting AutoPkgr-related success stories on the Linde Group website, and we'd love for you to share your story if you feel so inclined!
Have a great day.
AutoPkgr 1.3.1 is a minor update that focuses on fixing a couple bugs and adding some small features.
- Now supports GitHub two-factor authentication for generation of API tokens. (#393)
- Made Slack and HipChat output more verbose, including errors. (#417)
- Changed the way a valid user is determined when adding a schedule. Users not physically logged into the system can now enable the schedule assuming they have a valid home directory, and a
com.github.autopkg.plistpreference file. (#416)
- Adjusted a few things that should improve AutoPkgr's behavior when running on Mac OS X 10.8.
- Fixed a bug that would cause proxy settings to be displayed incorrectly. (#399)
- Fixed a bug where schedule changes would not reload in-memory launchd schedule.
- Incorporates a new version of AHLaunchCtl, which improves the reliability of the schedule settings.
- Fixed a bug that would prevent JSSImporter-related defaults from getting set.
- Fixed a bug that would result in repos appearing twice in the repo table. (#406)
- Fixed a bug causing search results to be incorrectly formatted. (#410)
- Improved handling of git operations when using proxies.
- Resolved issue where Slack/HipChat settings were not saving properly in OS X El Capitan. (Note: AutoPkgr does not officially support El Capitan yet.)
- AutoPkgr no longer attempts to automatically correct or change JSS URLs entered through the "Configure JSSImporter" options. As long as the URL you enter is valid, you shouldn't notice this.
Do you love AutoPkgr? We want to hear from you! Take a minute and tell us how AutoPkgr has made your life easier.
As always, if you discover a reproducible bug, the best thing to do is submit an issue on GitHub. This is how bug fixes like the ones in 1.3.1 happen!