AutoPkgr 2.0 brings Universal compatibility, YAML recipe support, and multiple improvements and fixes to the table! Here's a short summary of what this release includes:

• Replaced the mailcore2 dependency with libcurl. AutoPkgr is now a fully Universal app and will now work without the need for Rosetta!
• Added support for YAML recipes! AutoPkgr shells out to AutoPkg's python for yaml recipes.
• Improvements in Munki version detection. No more unnecessary "updates" available when you already have the latest version of Munki installed!
• Improvements to the startup screen if AutoPkg is not installed when AutoPkgr first launches. No more blank screen!
• Removed the legacy JSSImporter integration to avoid confusion with JamfUploader. To get started with AutoPkgr and JamfUploader, please check out the AutoPkgr Wiki! For more information about JamfUploader processors, please review the JamfUploader Wiki.
• Updated build settings to enabling building on Xcode 16.4 and above without build conflicts.
• A big "Thank you!" to the great @homebysix for all his awesome contributions!
• A warm welcome to the new AutoPkg Wizard by the great Graham Pugh.

Changed

• AutoPkgr 2.0 requires a minimum of macOS 11.
• Universal support added. This PR removes mailcore2 dependency and replaces it with system libcurl for SMTP email sending. The new implementation in LGEmailNotification builds RFC 2822 messages directly and uses libcurl's SMTP API, supporting STARTTLS (port 587), implicit TLS (port 465), and plaintext connections. Resolves: #728, #731.
• AutoPkgr now supports .yaml recipes and they will now display in the recipe list! AutoPkgr will be able to display and run any recipe you like - even if those recipes are .yaml or have parent recipes that are .yaml. Please note that AutoPkgr's recipe list is still stored at ~/Library/Application Support/AutoPkgr/recipe_list.txt and can be edited with any text editor. Resolves: #672 #701 #667.
• JSSImporter is deprecated and has been removed. Resolves: #727.
• Build improvements. Resolves: #724.

PRs Included

• Update pods to enable building on Xcode 16.4 by @homebysix in #725
• Fix blank screen on startup if AutoPkg missing by @homebysix in #726
• Replace mailcore2 with libcurl, allowing Universal builds by @homebysix in #730
• Remove JSSImporter integration by @homebysix in #732
• Detect installed Munki version from package receipts by @homebysix in #733
• Add support for parsing YAML recipes by @homebysix in #734

Fixed

• Fixed an issue where AutoPkgr did not load the main page if AutoPkg was not already installed. Clicking on any of the other tabs (Repos & Recipes, Schedule, Notifications, or Integrations) will result in a clear alert indicating that both AutoPkg and Git are required to use AutoPkgr. Both AutoPkg and Git can be easily installed from the Install tab. You no longer need to install AutoPkg first on new Macs before installing AutoPkgr. This resolved the long-standing issue that results in a blank initial AutoPkgr window if AutoPkgr is launched without AutoPkg. Resolves: #718, #696, #679.
• Fixed an issue where AutoPkgr did not detect the correct version of Munki installed. AutoPkgr now correctly detects the installed Munki version by reading the macOS package receipts in /private/var/db/receipts/, taking the highest version across Munki's sub-packages. Resolves: #493, #595, #614, #659, and #694.

Full Changelog: v1.6.1...v2.0

AutoPkgr 1.6.1 updates the integration for the great JamfUploader by @grahampugh. AutoPkgr 1.6.1 removes the Connect button from the integration as it is deprecated and no longer necessary. Simply select Save and Close to save your URL, credentials, and CDP to start autopkg-ing with JamfUploader! To get started with AutoPkgr and JamfUploader, please check out the AutoPkgr Wiki! For more information about JamfUploader processors, please review the JamfUploader Wiki.

Changed

• AutoPkgr 1.6.1 removes the Connect button from the integration as it is deprecated and no longer necessary. Simply select Save and Close to save your URL, credentials, and CDP to start autopkg-ing with JamfUploader!
• Friendly PSA for AutoPkgr and Jamf Pro v11.5 and above: You do not need to enable basic authentication in Jamf Pro in order for AutoPkgr to work with JamfUploader. In the JamfUploader Integration pane, just click Save and Close. JamfUploader still works with AutoPkgr in Jamf Pro v11.5 and above. This has been tested and still works as expected.
• Updated the Jamf Pro integration instructions in the [AutoPkgr Wiki] (https://github.com/lindegroup/autopkgr/wiki/Jamf-Pro) to note that the Connect button is deprecated and has been removed.
• Updated the versions of Sparkle and OpenSSL-Universal.
• Due to the fact that macOS no longer ships with Python, you will now need to install AutoPkg first on new Macs before installing AutoPkgr. This gives AutoPkgr the path to Python it needs to run smoothly. If you already have AutoPkg installed, you already have the built in Python that ships with AutoPkg and can just install AutoPkgr.
• Due to the fact that there is no native YAML library for macOS, AutoPkgr does not support .yaml recipes and they will not display in the recipe list. However, AutoPkgr will be able to run any recipe you like via your recipe list (even if those recipes are .yaml and are added to your recipe list manually, or have parent recipes that are .yaml). AutoPkgr's recipe list is stored at ~/Library/Application Support/AutoPkgr/recipe_list.txt and can be edited with any text editor.

Fixed

• Fixed an issue where placeholder text for the recipe checkbox was improperly rendered behind the text of recipe list entries.
• Please note that JSSImporter has been deprecated and you should use JamfUploader instead. You can find the instructions to configure the Jamf Pro integration in the [AutoPkgr Wiki] (https://github.com/lindegroup/autopkgr/wiki/Jamf-Pro).
]]> 10.13 Thurs, 20 June 2024 09:00:00 -0700 To JamfUploader and Beyond!

AutoPkgr 1.6 adds integration for the great JamfUploader by @grahampugh, a shiny new icon, as well as new notification templates for JamfUploader processors with Slack, Teams, Google Chat, and email! To get started with AutoPkgr and JamfUploader, please check out the AutoPkgr Wiki! For more information about JamfUploader processors, please review the JamfUploader Wiki.

Added

• AutoPkgr 1.6 adds integration for the great JamfUploader by @grahampugh!
• AutoPkgr 1.6 adds a shiny new icon!
• AutoPkgr 1.6 adds new notification templates for JamfUploader processors with Slack, Teams, Google Chat, and email! If your recipe uses one of the following processors, AutoPkgr will notify you with the summary_result of each!
  • jamfcategoryuploader
  • jamfcomputergroupuploader
  • jamfdockitemuploader
  • jamfextensionattributeuploader
  • jamfpackageuploader
  • jamfpatchuploader
  • jamfpolicyuploader
  • jamfscriptuploader

Changed

• Due to the fact that macOS no longer ships with Python, you will now need to install AutoPkg first on new Macs before installing AutoPkgr. This gives AutoPkgr the path to Python it needs to run smoothly. If you already have AutoPkg installed, you already have the built in Python that ships with AutoPkg and can just install AutoPkgr.
• Due to the fact that there is no native YAML library for macOS, AutoPkgr does not support .yaml recipes and they will not display in the recipe list. However, AutoPkgr will be able to run any recipe you like via your recipe list (even if those recipes are .yaml and are added to your recipe list manually, or have parent recipes that are .yaml). AutoPkgr's recipe list is stored at ~/Library/Application Support/AutoPkgr/recipe_list.txt and can be edited with any text editor.
• Moved instructions from the README to the Wiki. If you need help, we recommend that you check out the AutoPkgr Wiki!

Fixed

• Set AutoPkgr's Python launchPath to /usr/local/autopkg/python. Using AutoPkgr should no longer cause macOS to warn that "AutoPkgr needs to be updated." This will also avoid issues as AutoPkg versions increase.
• Corrected the formatting for the JSSImporter template. Please note that while still included as an integration, JSSImporter has now been deprecated and you should use JamfUploader instead.
]]> 10.13 Fri, 10 June 2022 12:00:00 -0700 Fix it up!

AutoPkgr 1.5.7 includes a bug fix for integration and repo compatibility.

Fixed

• Corrected default branch invocation to avoid issues when working with integrations and repos. This resolves issue #665 and #668. Thanks to @apizz and @jaw4uz for the reports!
• Issue #666, unrelated to AutoPkgr has been resolved by the release of AutoPkg 2.3.1. Thanks to @homebysix for #723 and #724 for the reports and fixes!
]]> 10.13 Fri, 05 March 2021 12:00:00 -0700 Making a list.. Checking it.. once

AutoPkgr 1.5.6 includes some fixes when working with .munki recipes.

Changed

• Updated Sparkle and AutoUpdate to use Universal version. Please note that AutoPkgr is not a Universal app and requires Rosetta on Apple Silicon Macs, due to some legacy dependencies.

Fixed

• Attention Munki Users: AutoPkgr will once again automatically add the MakeCatalogs.munki recipe to the end of your recipe list and keep it there. You do not have to check the box to include the MakeCatalogs.munki in your schedule. It will be included automatically. Since the introduction of recipe trust information in AutoPkg 1.0, we recommend that you create an override of MakeCatalogs.munki, instead of running the recipe itself.
• Updated default branch invocation to avoid branch name issues when working with repos.
]]> 10.13 Tue, 23 February 2021 12:00:00 -0700 A Simple Integration

AutoPkgr 1.5.5 now integrates with SimpleMDM! The SimpleMDM Munki repo plugin works with Munki and AutoPkg to import packages via .munki recipes. To get started with AutoPkgr and SimpleMDM, please check out the AutoPkgr Wiki! For more information about the SimpleMDM Munki repo plugin, please review the README.

Added

• AutoPkgr now integrates with the SimpleMDM munki repo plugin. Big thanks to @tboyko for a great collaboration!

Changed

• Attention Munki Users: In order to eliminate confusion, AutoPkgr will no longer automatically add the MakeCatalogs.munki recipe to the end of your recipe list. If you would like to add it, you should create an override of the MakeCatalogs.munki recipe and add it to your recipe list. Since the introduction of recipe trust information in AutoPkg 1.0, we recommend that you create an override of MakeCatalogs.munki, instead of running the recipe itself. Make sure to check the box to include the MakeCatalogs.munki in your schedule. It will no longer be included automatically.
• Updated the Folders & Integrations tab to "Integrations."
• The minimum macOS build to run AutoPkgr is now macOS 10.13. It is recommended to run at least macOS 10.13.6 with AutoPkgr. 10.14.6 and above is even better. If you need to run below macOS 10.13, please consider using version 1.5.4 or below of AutoPkgr.
• Updated ongoing development credits.

Fixed

• Updated to Google Chat verbiage (in place of Hangouts).
• Updated the "AutoPkgr Google Chat" Template. This no longer needs to be edited.
]]> 10.13 Tue, 22 September 2020 12:00:00 -0700 The Notification Club

Don't you.. forget about Teams (or Hangouts). Let's get together. AutoPkgr 1.5.4 now integrates notifications with Microsoft Teams and Google Hangouts!









Added

• AutoPkgr now integrates with Microsoft Teams and Google Hangouts for notifications.
• For Hangouts, copy the "AutoPkgr Slack Bot" Template into the "AutoPkgr Google Hangouts" Template and select Save.

Fixed

• Improved notification error handling.
]]> 10.9 Tue, 28 July 2020 12:00:00 -0700 Darkmode Duck!

Let's get legible. Text in AutoPkgr 1.5.3 is now much more legible in macOS Dark Mode. Semantic colors to the rescue!






Fixed

• AutoPkgr now supports semantic colors in panels and popovers for better compatibility with macOS Dark Mode. Thanks to @apizz in issue #633 for the report.
• Updated integration credits to support semantic color, updated names, and removed dates.
]]> 10.9 Fri, 08 May 2020 10:00:00 -0700 Armageddon It!!

To celebrate the upcoming release of AutoPkg 2.0, the 1.5.2 release of AutoPkgr now supports the latest release version of the AutoPkg command line utility! If you use JSSImporter, or any custom processors, please review the following before installing AutoPkg 2.0: https://github.com/lindegroup/autopkgr/wiki/AutoPkg-2.0-transition-notes-for-AutoPkgr-users.

Added

• AutoPkgr now supports the latest release version of the AutoPkg command line utility. This adds compatibility with the upcoming version 2.0 of AutoPkg, which runs in Python 3 only. Big thanks to @homebysix for the help!
]]> 10.9 Fri, 24 Jan 2020 12:00:00 -0700 Norwegian Blues stun easily, major.

To celebrate the new release of JSSImporter, this release now reports and installs the correct current release version of JSSImporter! This release again implements Apple's security requirements for macOS 10.15 compatibility: hardened runtime, complete code signing, Notarization with the Apple Notary Service, and stapling of tickets.

Added

• AutoPkgr now reports and installs the latest release version of JSSImporter (currently v1.0.2).

Changed

• Updated all package, identifier, and url references of sheacraig/jssimporter to jssimporter/jssimporter, and its copyright for compatibility with @grahampugh's release.
• Updated example url in AutoPkgr's Folders & Integrations tab for JSSimporter to reflect Jamf branding.
• Updated language in AutoPkgr's Notifications tab to macOS to reflect Apple branding.
• Updated credits.
• Updated version to 1.5.1.
• Updated build number to 1404.
• Updated CHANGELOG.md.
• Updated development team in README.md.
• Per Apple's Notarization requirements, the Notarized AutoPkgr-1.5.1.dmg has been stapled with the tickets from the Apple Notary Service. This allows full compatibility with GateKeeper for installation and ongoing checks in macOS Catalina. Due to this, if you build from source code instead of installing AutoPkgr with the dmg, AutoPkgr may not launch in macOS Catalina.
]]> 10.9 Tue, 1 Oct 2019 12:00:00 -0700 The True Love Update - It's only mostly dead.

In preparation for the release of macOS Catalina, we've made a new version of AutoPkgr. This release implements Apple's security requirements for macOS 10.15 compatibility: hardened runtime, complete code signing, Notarization with the Apple Notary Service, and stapling of tickets.

We've also added support for the awesome Dark mode in macOS 10.14+, an easy right-click action for Update Trust Info for Override, and an updated code signing certificate.

AutoPkgr 1.5 enables macOS administrators everywhere to continue using AutoPkgr. Happy autopkg-ing!

Added

• Support for Dark Mode in macOS 10.14+.
• Hardened Runtime and complete Code Signing to support macOS Catalina.
• Notarization from Apple to support macOS Catalina.
• New code signing certificate valid until 2024.
• "Update Trust Info for Override" right-click action.
• Spanish localization. (big thanks to @luisgiraldo for translating!)
• Added OpenSSL-OSX pod in podfile.

Changed

• Updated credits and copyright information.
• Updated README.md to reflect Jamf and macOS rebranding.
• Per Apple's Notarization requirements, the Notarized AutoPkgr-1.5.dmg has been stapled with the tickets from the Apple Notary Service. This allows full compatibility with GateKeeper when installing in macOS Catalina. Due to this, if you build from source code instead of installing AutoPkgr with the dmg, AutoPkgr may not launch in macOS Catalina.
]]> 10.9 Tue, 30 Jul 2019 12:00:00 -0700 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).

If you have any questions, find us on Slack or Google Groups. If you find a reproducible bug, we'd love it if you'd open an issue on GitHub. Thanks!

 

Added

• One-click integration with @hjuutilainen's VirusTotalAnalyzer processor. (#503)

Changed

• 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

• 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

• Removed 10.8 support. AutoPkgr now requires Mac OS X 10.9 or higher.
]]> 10.9 Mon, 3 Oct 2016 10:00:00 -0700 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:

Added

• 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

• 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.

Changed

• 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.

Security

• 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 security command 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 security command 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.

 

As always, please submit any issues you find on GitHub, or find us on Slack or Google Groups if you have questions. Have a great week!

]]> 10.8 Mon, 2 May 2016 10:00:00 -0700 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!

Added

• 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

• 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.

Changed

• 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.
]]> 10.8 Tue, 1 March 2016 14:00:00 -0700 AutoPkgr 1.3.2 is now available, and fixes a couple bugs that were reported by the community.

Added

• You can now specify the name of the AutoPkgr bot when configuring Slack integration. (#437)

Changed

• Now includes localized hostname in all notifications, not just email.

Fixed

• 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.

]]> 10.8 Fri, 18 September 2015 11:00:00 -0700 AutoPkgr 1.3.1 is a minor update that focuses on fixing a couple bugs and adding some small features.

Added

• Now supports GitHub two-factor authentication for generation of API tokens. (#393)
• Made Slack and HipChat output more verbose, including errors. (#417)

Changed

• 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.plist preference file. (#416)

Fixed

• 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.)

Removed

• 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!

Happy packaging.

]]> Wed, 19 August 2015 16:15:00 -0700 We're proud to announce AutoPkgr 1.3, with a ton of new features and improvements.

Along with integration with Absolute Manage and MacPatch, there are new scheduling options (running at a specific time every day) and notification options (notifying a Slack or HipChat channel). We've also polished and refined the interface, and reworked the back-end to more easily support future integration with other AutoPkg processors.

See a full list of the changes below:

Added

• Integration with Absolute Manage (via the AbsoluteManageExport processor). (#217)
• Integration with MacPatch (via the MacPatchImporter processor). (#347)
• Now you can send notifications directly to a Slack (#358) or HipChat (#359) channel.
• More flexible options for scheduling AutoPkg to run. New daily and weekly options! (#361)
• By popular request, you can now right-click on a recipe and choose Run This Recipe. (#107)
• You can also right-click on a recipe in the list and choose Get Info to see various details about the recipe. (#342, #357, #370)
• Right-click on a repo to access the GitHub commits page or update a single repo. (#357)
• The repo and recipe lists are now sortable! (#356)
• The repos list now displays the number of stars each repo has on GitHub (and you can sort by them too). (#356, #357)
• Proxy configuration is now much easier than typing Terminal commands. Just go to the Folders & Integration tab, then click on Configure AutoPkg to access the proxy settings.
• In the same location as the proxy settings, you can now create the GitHub API token used with autopkg search feature using AutoPkgr. This allows a greater number of search queries per hour.
• The install tab now displays status of additional integrated tools and processors, like AbsoluteManageExport and MacPatchImporter.
• Easier uninstallation of components like JSSImporter and AbsoluteManagerExport. (#332)
• Better validation of the standard output AutoPkgr receives from AutoPkg.
• Ability to change the Git binary used by AutoPkg.
• The repos list now has a status indicator showing if there are new commits to an installed repo. (#357)
• The recipe list now has a status indicator showing if a recipe is missing a parent recipe. (#357, #370)
• We're now using OS X Notification Center for a few useful messages, like when new software has been packaged by AutoPkg. (#79)
• Added the ability to configure how often notifications are sent for new version of AutoPkg, JSSImporter, Git, and other components. (#379)
• Added a "Check for AutoPkgr Updates" item in the AutoPkgr menu extra. (#275, #312)

Changed

• New JSSImporter users will now get the "official" jss-recipes repo when configuring JSSImporter. Note: Existing JSSImporter users will not (yet) be affected, but will eventually need to transition to the new repo. Instructions will be available soon. In the meantime, read through the jss-recipes readme!
• Reworked Folders & Integration tab interface to support a theorically unlimited number of integration tools, including Munki, Casper, Absolute Manage, and MacPatch. The sky is the limit.
• Updated readme to make it clear that you should only update repos before every AutoPkg run if you trust recipe authors.
• Removed unused menus and menu items.
• Significantly rewrote the readme with new and updated information.
• Behind-the-scenes code cleanup, typo fixes, refactors, and reorganization. Always tidying up!

Fixed

• Fixed a bug that could prevent email configuration changes from "sticking."
• Squished a bug that could cause the JSS_VERIFY_SSL key to be incorrectly set.
• Stomped on a bug that resulted in a "(null)" error in certain circumstances. (#352)
• Swatted a bug that required pressing Tab or Enter in order to save the email password before sending a test email. Now the password is saved upon clicking the Send Test Email button as well. (#352)
• When a JSSImporter update was available, the text on the Install tab would often overflow its container. We've enlarged the container, so hopefully that won't happen now. (#314)
• AutoPkgr now remembers the last window position and table sort status upon subsequent launches. (#375)
• Squashed a bug that resulted in "Version (null)" in OS X notifications. (#376)
• Eradicated a bug that could cause AutoPkgr to falsely believe there are multiple instances of AutoPkg running.

We don't just love community feedback; we require it! AutoPkgr wouldn't be as cool as it is without the input from Mac admins who use it. Get in touch with us and let us know what you think.

To get help with AutoPkgr, you can find us on our Google Group or submit an issue on GitHub. You can also sometimes get help and ideas on the MacAdmins Slack channel. Also, we've greatly expanded the Troubleshooting section of our readme, so please do check that out.

Hope you love it!

]]> Fri, 24 July 2015 10:00:00 -0700 Hello friends! We've got a new version of AutoPkgr for you. This has a few small fixes and changes, including more friendly display of the "Last AutoPkg Run" status in the menu and a long-awaited fix to a problem reported by a few Chrome users.

Changed

• Now you can check the SSL box even if you're not using SMTP authentication. (#335)
• Relative date/time now shown in AutoPkgr menu status (e.g. "Today at 8:00 AM"). (#340)

Fixed

• Fixed a particularly devious bug that would cause AutoPkgr to get stuck running recipes while certain apps (usually Google Chrome) were active. (#230)
• AutoPkgr menu status should now be up to date upon first click, not just upon status change. (#340)
• Fixed a bug that caused progress indicators to show inaccurate counts when the StopProcessingIf processor is present in a recipe. (#333)
• Reduced the odds of error messages overflowing the on-screen alert dialog boxes.
• AutoPkgr now asks for XML when talking to your JSS, but should successfully revert to JSON if your JSS stubbornly refuses. (#287)
• Fixed a minor bug that could result in excess CPU usage.
• Various minor cosmetic changes.

Security

• Updated to the most recent version of the AFNetworking components.

We're constantly improving AutoPkgr based on community feedback. If you have ideas for future features, if you want to report a bug, or if you just have questions about using AutoPkgr, the best way to get in touch with us is to submit an issue on GitHub. If you don't have or want a GitHub account, you can also reach us at the autopkgr-discuss Google group. Thank you!

]]> Fri, 8 May 2015 12:00:00 -0700 Welcome to AutoPkgr 1.2.2! This is a minor update focused on supporting upcoming changes in how AutoPkg reports its actions.

Added

• Compatibility with upcoming changes to AutoPkg reporting format.
• Updated documentation to include information about creating/editing overrides.
• Items in Help menu now link to useful URLs. (#12)

Changed

• AutoPkgr now prevents you from proceeding beyond the Install tab if you don't have AutoPkg and Git installed. (#325)

If you have any issues with AutoPkgr, please submit an issue on GitHub. We always welcome your feedback.

Thank you!

]]> Thu, 16 Apr 2015 12:00:00 -0700 Following up on our big 1.2 release, we've released 1.2.1 with a few bug fixes and enhancements:

Added

• Created changelog.
• AutoPkgr now displays the version number of Git and AutoPkg in the Install tab. (#244)
• Now you'll receive an email when new versions of Git, AutoPkg, or AutoPkgr are available. (#137)

Security

• Now using three-way encryption to store SMTP password more securely. (#271)
• Improved security of the helper tool AutoPkgr uses to run in the background.
• AutoPkgr now tries to obfuscate sharepoint usernames and passwords in email notifications. (#227)

Fixed

• Background run not updating date in status menu. (#286)
• Resolved an issue that prevented "Launch at Login" button from working in 10.8 and 10.9. (#272)
• Prevented displaying progress detail messages unnecessarily.
• Properly processes %20 in URLs when parsing versions. (#270)
• Fixed the "Check for repo updates before each recipe run" checkbox wording.
• Fixed a bug that prevented status messages over 50 characters from being displayed in the menu.
• Fixed a bug that prevented autopkg run status from appearing in the menu.
• Made configuration options for "Run AutoPkg Now" consistent with menu items.
• Fixed a situation that prevented launchd from reading current defaults values. (#296)
• Now showing AutoPkgr icon in both the Dock and the menu bar by default.
• Small improvements to keychain migration method.

Changed

• Uninstall is now handled by the main app, not the helper tool.

As always, if you find any bugs or encounter problems, we welcome you to open a new issue on GitHub. Thank you!

]]> Sun, 8 Mar 2015 17:00:00 -0800 We're delighted to introduce you to version 1.2 of AutoPkgr. There are a few major new features in this release, as well as numerous bug fixes.

Important: After upgrading to version 1.2, you will need to reenter your email password in the AutoPkgr Schedule tab to continue getting email notifications.

New Features and Enhancements:

• By popular request, scheduling will now be handled by a LaunchDaemon. This allows AutoPkgr to continue running after a restart, even if nobody is logged in. (#72)
• You can now set how AutoPgkr is displayed, either as a menu item, Dock item, or both. (#10)
• You can now set AutoPkgr to launch at login. (#11)
• If the "check for repo updates" option is enabled, it will now perform the repo update prior to each autopkg run, rather than just when AutoPkgr is launched. This should help next time the AdobeFlashPlayer recipe changes rapidly.
• AutoPkgr now passes the recipe and override identifier into AutoPkg to avoid naming clashes when multiple repos have recipes with the same name. Thanks to @rtrouton for the suggestion. (#208)
• The AutoPkgr menu has been redesigned and enhanced with new menu options.
• Progress is now displayed during repo-update.
• We now use OS X's Notifications feature to display test email success. More notifications coming soon!
• Creating an override will now prompt for override name, allowing for the creation of multiple overrides with the same parent. (For example, FirefoxSelfService.jss and FirefoxAutoUpdate.jss.)
• When enabling a recipe, if the parent recipe is not installed, an alert will be displayed.
• Scheduled recipes will automatically be removed from the recipe list if their repo is removed, or if a repo update no longer contains the recipe.
• You can now search GitHub for AutoPkg recipes, equivalent to autopkg search [recipe].
• Easy uninstall! If you ever want to uninstall AutoPkgr and its components, hold the Option key and choose Uninstall from the AutoPkgr menu icon.

Changes:

• New keychain item for AutoPkgr located at ~/Library/Keychains/AutoPkgr.keychain. It can be unlocked and examined using the computer's serial number as the password.
• Using master JDS is now set with a checkbox. Thanks to @everetteallen for this suggestion. (#174)

Bug-Fixes:

• Fixed a condition that could cause preferences to be erased if an error occurs during launch.
• Fixed a condition that could cause AutoPkgr to hang due to Python stdout buffer not getting flushed.
• Fixed a condition where keychain was queried for email password even when authentication was not enabled.
• Automatically removes trailing slash from JSS_URL which could cause 404 errors. Thanks to @acodega for getting to the bottom of this! (#221)
• Minor typo fixes and additional log entries, as always.

Note for proxy users:

• If using proxies that require authentication you will not be able to use the system proxies configured in the system preferences via the defaults write com.lindegroup.AutoPkgr useSystemProxies -bool true. Specify the the proxy setting manually using defaults using the instructions in the readme. We'll hopefully be adding a UI element to a future release. This only applies to proxies that require authentication.

As always, if you find any bugs or encounter problems, please open a new issue on GitHub and we'll do our best to help troubleshoot. Thank you!

]]> Thu, 12 Feb 2015 12:00:00 -0800 Our cousin project jss-autopkg-addon is now JSSImporter, so we had to make some changes to the guts of AutoPkgr in order to remain compatible.

This update is recommended for anybody who is using AutoPkgr to integrate with their JSS.

Bug fixes

• Updated all references from jss-autopkg-addon to JSSImporter. This should resolve a problem that prevented AutoPkgr from properly installing or upgrading JSSImporter on many systems.

Enhancements

• Removed parts of the code that we no longer use, like an unzipper class.
• Typo fixes, mostly internal.

As always, please open an issue on GitHub if you find a reproducible problem. We're happy to help troubleshoot!

Thank you!

]]> Mon, 15 Dec 2014 17:00:00 +0000 Some small tweaks for 1.1.2, centered mostly around compatibility with the latest version of jss-autopkg-addon.

Important Changes

• If using JSS integration, python-jss now automatically "URL encodes" the distribution point passwords (#177). If you have a password with special characters, and have manually constructed it with proper URL encoding, it will no longer work. You should now just set it to the actual password.

Bug fixes

• Fixed a bug which would set SSL_VERIFY incorrectly for Casper environments with self-signed certificates.
• Made GUI elements match more consistently between OS X Mavericks and OS X Yosemite.
• Fixed a bug that caused errors in environments with a password-protected proxy.
• Corrected spelling of "available" in email notifications and other places.

Enhancements

• Made compatible with latest release of jss-autopkg-addon.
• Updated readme to clarify that Casper 9 or newer is required for JSS integration.
• AutoPkgr now does not remove @sheagcraig's jss-recipes repository when the JSS settings have been cleared.

As always, please open an issue on GitHub if you find a reproducible problem.

Thank you!

]]> Mon, 1 Dec 2014 23:00:00 +0000 Version 1.1.1 brings us a few bug fixes and minor improvements:

Bug Fixes

• Address issues with JSS integration:
  • Better handling of URLs for Cloud hosted JSS. (#170)
  • More comprehensive logging relating to JSS operations.
• Cleaner UI error messages. (related to #167)
• Correctly detects Xcode git. (#181)
• Compatibility with Yosemite's "dark mode." (#190)
• Minor GUI adjustments.

Enhancements

• Better proxy support. AutoPkgr can now use proxies set in System Preferences, including Auto Detected WPAD/PAC.

  defaults write com.lindegroup.AutoPkgr useSystemProxies -bool true
                          

  Note: You must make sure to include any domains and servers you do not want to use a proxy to access in the "Bypass proxies for these Domains & Hosts" setting.

  Note: Proxy support is still in early development and we would appreciate feedback as to how it's working, both good and bad. There's an open issue about proxies; please visit and comment.

  See the README.md for more detailed information.

Known Issues

• Currently there is a condition that can cause the JSS_VERIFY_SSL to be incorrectly set when using self signed certificates or certificates singed by an untrusted CA. If using one of these and having trouble running .jss recipes you may need to manually set the key to false,
  

    defaults write com.github.autopkg JSS_VERIFY_SSL -bool false
                

As always, if you have any problems with AutoPkgr, please head over to our Google Group and let us know. If it's a reproducible bug, please open an issue on GitHub with as much detail as possible.

]]> Sat, 15 Nov 2014 16:00:00 +0000 We're happy to announce the next major release of AutoPkgr. This one has some major new features and a few minor improvements as well.

As always, community feedback is welcomed. If you have a question, the Google Group is a good place to ask it. If you find a reproducible problem, please open/update an issue on GitHub.

New Features

• Added built-in support for integrating with JAMF's Casper Suite (#75):

  • The newly-renamed Folders & Integration tab provides easy access to JSS URL and API settings.
  • Upon entering valid JSS information, AutoPkgr automatically installs the latest version of @sheagcraig's jss-autopkg-addon and adds some ready-to-use .jss recipes.
  • The .jss recipes you subscribe to will automatically produce smart groups and Self Service policies scoped to a "Testing" group.
  • The policy creation behavior can be tweaked and customized with XML template files.
  • AutoPkgr keeps you up to date when new versions of the jss-autopkg-addon are released.

  For more details on setting up automatic updates with AutoPkgr and Casper, read Auto Update Magic.

  Thanks to @sheagcraig for major help incorporating his jss-autopkg-addon framework and advising on JSS workflow practices.



• Added support for creating recipe overrides (#60):

  • Right-clicking / Control-clicking on a recipe will allow creation/editing of an override.
  • Ability to choose your preferred text editor for editing overrides.

• Added environmental proxy support (#152 and #130):

  • Equivalent to this shell command: export HTTP_PROXY=http://proxy:8080
  • To use HTTP proxy: defaults write com.lindegroup.AutoPkgr HTTP_PROXY http://proxy:8080
  • To use HTTPS proxy: defaults write com.lindegroup.AutoPkgr HTTPS_PROXY https://proxy:8080
  • To stop using HTTP proxy: defaults remove com.lindegroup.AutoPkgr HTTP_PROXY
  • To stop using HTTPS proxy: defaults remove com.lindegroup.AutoPkgr HTTPS_PROXY
    Note: This will not create or modify any system proxy settings; it will only add them to your shell env.

Improvements

• Improved readme with detailed information on Munki and Casper integration, and some troubleshooting tips.
• Additional detail added to logs.
• Better version reporting in email messages (especially with .munki recipes).
• More concise errors when Python exceptions occur.

Bug Fixes

• Fixed bug that prevented certain repos from appearing automatically in the repos list (#148).
]]> Wed, 22 Oct 2014 18:17:45 +0000 Numerous changes and bug fixes this time around, including:
• The ability to cancel installations, recipe checks, and other tasks in progress.
• More detail in logs, including the ability to enable a verbose log mode for troubleshooting (see readme).
• Improved behavior of the "Open in Finder" buttons.
• Resolved bug that would cause an incorrect hostname to be reported in notification emails.
• Resolved bug that would prevent "from" address from appearing in log output.
• Implemented code signing to avoid "unidentified developer" error upon first launch.
• Now using the Sparkle framework, so AutoPkgr can keep itself up to date.
• Git install feature is now available for Macs running 10.8.
• Git installer for 10.9 no longer relies on the Xcode command line tools. No need to leave AutoPkgr to get Git!

We rely on community feedback to improve the app and fix bugs. We have a Google Group for general discussion, and if you find a reproducible bug or have a specific feature request, please open an issue on GitHub with as much detail as possible. Thank you!

]]> Mon, 24 Sep 2014 09:40:00 +0000