This is the official release of AutoPkg 1.0. There were no changes from Release Candidate 1.
1.0.0 (November 16, 2016)
ADDITIONS:
- New
audit
verb, used to output helpful information about any recipes that:- Are missing a CodeSignatureVerifier step
- Use non-HTTP URLs for downloads
- Supply their own processors and thus will run code not provided by AutoPkg itself
- Use processors that may potentially be modifying the original software
downloaded from the vendor
- New
verify-trust-info
andupdate-trust-info
verbs. These can be used to
add "trust" hash information to a recipe override. If a parent recipe and/or
its processor(s) is later updated (typically via a third-party recipe repo and
runningautopkg repo-update
against this or all recipe repos), this
trust information will be invalid and prevent the recipe from running
until the trust information has been updated. Runningverify-trust-info
with
additional verbosity will print out full diffs of upstream changes made since
the last trust information was recorded, andupdate-trust-info
will update
it to match the current state of parent recipes. This behaviour can be bypassed
using theFAIL_RECIPES_WITHOUT_TRUST_INFO
AutoPkg preference. See the
wiki article for more information. - New
AppPkgCreator
processor, a single processor replacing the several steps
previously required for building a package from an application bundle. - Support for "rich" recipe lists in property list format, which can specify
pre/post-processors and additional input variables for that specific run. See the
Running Multpiple Recipes article for more details.
FIXES:
- Fix SparkleUpdateInfoProvider ignoring
appcast_request_headers
argument since
switching from urllib2 to curl. (GH-277) - Miscellaneous fixes to better handle unicode in
autopkg
message output.
(GH-299) - Fix GitHub API error on
autopkg search
for a recipe name containing spaces.
(GH-305)
IMPROVEMENTS:
- URLDownloader now passes
--fail
option so that most 400-class error codes
will result in a failed recipe run. (GH-284) - AutoPkg now reports an exit code of
70
if any recipe in anautopkg run
fails. Eventually other exit codes may later be added to report on other
specific behavior. (GH-297) - MunkiImporter now accepts an
uninstaller_pkg_path
input variable, used to
copy Adobe uninstaller packages and setuninstaller_item_location
in pkginfos. - MunkiImporter should now be able to detect existing Adobe CCP-built package
items in a Munki repo as generated bymakepkginfo
in Munki tools version 2.8.0
and higher.