I run both Munki and AutoPkg.
I currently and for a while use the AurtoPkg recipe you wrote to get the MacAdmins hosted signed version of MunkiTools.
This historically and usually would create separate entries in Munki representing each individual sub-component so that as needed just an individual sub-component e.g. just the Managed Software Center app could be updated rather than all the components.
The last time such a full set appeared via AutoPkg and your recipe was for the 6.6.0 release. This via the AutoPkg recipe was added to (my) Munki repo in the 'testing' catalog which is the usual behaviour for munki recipes.
Since then the behaviour has changed, there have been 6.6.1, 6.6.2 and this week 6.6.3 recipes all of which via your AutoPkg recipe are instead added to a 'development' catalog. Furthermore the name of the imported installer pkg now indicates it is a single combined installer.
I therefore have two queries.
- Being that your recipe labels it as development but the GitHub site implies it is an official release, should we treat it as being pre-release i.e. development or not?
- Is it supposed to now be a combined single installer pkg, is there any drawback to this?
Note: As far asI can see I believe the recipe for the non-code signed version also has this new behaviour