Release v1.24.1

Changed

• Skipped AutoPkg recipe type convention checks when type is unknown. (#55)
• Updated release documentation to reflect new automated workflow.
• Built error handling into release automation workflow.

Release v1.24.0

Added

• Automated GitHub Actions workflow for creating releases and bumping versions.

Changed

• Updated CodeQL workflow to run on main branch instead of master.

v1.23.0

Added

• Added support for minimum AutoPkg version validation for new VariableSetter processor.
• check-munkiadmin-scripts and check-outset-scripts now support the --valid-shebangs argument for specifying additional valid interpreter paths.

Changed

• check-munki-pkgsinfo now skips warning about missing packages if a PackageCompleteURL key is set in the pkginfo.

v1.22.1

Added

• Added support for minimum AutoPkg version validation for new VariableSetter processor.

Changed

• check-munki-pkgsinfo now skips warning about missing packages if a PackageCompleteURL key is set in the pkginfo.

v1.22.0

Changed

• format-xml-plist hook now uses Python's plistlib instead of macOS's plutil. This enables compatibility with a wider selection of CI/CD runners, including pre-commit.ci.

v1.21.1

Fixed

• Fixed bug in check-autopkg-recipes that would flag processors as "not conventional" for recipe types that have multiple filename hints. Realistically, this only affected .jamf or .jamf-upload recipe types.

v1.21.0

Added

• check-munki-pkgsinfo now detects the incorrect key condition and suggests using installable_condition instead.

Changed

• Renamed internal package from pre_commit_hooks to pre_commit_macadmin_hooks to resolve namespace collision with the official pre_commit_hooks package. (#78)

v1.20.0

Added

• check-autopkg-recipes and check-munki-pkgsinfo now validates that supported_architectures values are set appropriately.
• In anticipation of Munki 7, check-munki-pkgsinfo validates that version_script is a string starting with a script shebang.
• check-munki-pkgsinfo now checks for specific deprecated installer_type and uninstall_method values, most of which are detailed here.
• Added new FindAndReplace core processor version requirements for AutoPkg recipes.

Changed

• Improvements to check-preference-manifests hook. (#91, thanks to @relgit)
• check-autopkg-recipes ignores supported_architectures values within Munki pkginfo dictionaries that appear to be AutoPkg recipe substitution variables (e.g. %ARCH%).

v1.19.0

Added

• Added --warn-on-missing-installer-items flag that makes missing Munki install/uninstall items a warning instead of a failure. (#86, thanks to @haircut)
• Apply the same checks to uninstaller_item_location that were previously applied to installer_item_location.
• check-autopkg-recipes requires Munki recipe pkginfo dicts to contain at least name and description.
• check-autopkg-recipes now validates that uninstall_method and uninstall_script are set appropriately in Munki recipes.

Changed

• check-autopkg-recipes includes jamf-upload as an AutoPkg recipe type, and updated processors included in jamf/jamf-upload recipe convention.
• check-munki-pkgsinfo requires a version key in addition to name and description.

Fixed

• Bug fix in check-munkiadmin-scripts that prevented script names from processing correctly.
• Bug fix in check-munki-pkgsinfo that prevented --warn-on-duplicate-imports flag from working correctly.

v1.18.0

Added

• check-munki-pkgsinfo now produces an error if uninstall_method is set to uninstall_script but no uninstall script is present in the pkginfo.
• check-munki-pkgsinfo now checks for deprecated pkginfo keys.
• check-munki-pkgsinfo now includes checks for many possible pkginfo key typos, not just minimum_os_version and maximum_os_version. Suggestions welcome if you think of more.
• check-munkiadmin-scripts now checks whether scripts are named correctly, not just executable.