For the Safari ElCap and Sierra 11.0.2 released by Apple the other day, 11.0.2 was released last month but a different build of 11.0.2 was released earlier this week.
The fixlets IBM released are non-relevant on a Sierra machine with version 11.0.2 (12604.4.7.1.2) when Version 11.0.2 (12604.4.7.1.6) is what Apple just released.
This happens because the relevance is looking for just version 11.0.2 and not the build ((version (version of application "Safari.app" as string & ".0.0") < "11.0.2" as version ) or (version of application "Safari.app" as string = "9.0" as string))
I modified the fixlets and added for ElCap:
exists strings whose (it as string < “11604.4.7.1.6”) of values of entries whose (key of it = “CFBundleVersion”) of dictionaries of files “/Applications/Safari.app/Contents/Info.plist”)
and Sierra:
exists strings whose (it as string < “12604.4.7.1.6”) of values of entries whose (key of it = “CFBundleVersion”) of dictionaries of files “/Applications/Safari.app/Contents/Info.plist”)
And that is working on over 100 QA machines so far.
Version 11.0.2 (11604.4.7.1.6) on OS X El Capitan 10.11.6
Version 11.0.2 (12604.4.7.1.6) on macOS Sierra 10.12.6
For High Sierra, it appears the Safari Update is contained in the Supplemental Update only as my colleague and I verified Safari’s version alongside the softwareupdate command line, and no Safari updates showed up - just the Supplemental Update as expected for 10.13.2.
Also, Fixlet #10130005 was superseded and now shows “UPDATE: macOS High Sierra 10.13.2 Available (Superseded)” - however, it is a supplemental update to existing 10.13.2 installations. Fixlet #10130005 gets < 10.13.2 machines up to the current version of High Sierra.