4 ms·
One plausible reason is that they’ve already released a 10.13.1 beta, announced features and API changes coming in 10.13.1, and started revising documentation t
by jasomill 9y ago
One plausible reason is that they’ve already released a 10.13.1 beta, announced features and API changes coming in 10.13.1, and started revising documentation to reflect changes introduced in 10.13.1, so branding today’s update “10.13.1” would result in a nontrivial amount of extra work and confusion, in exchange for...what, exactly?
The updated version does come with a new full App Store installer and build number (17A405), however, so it’s as easy to install and identify programmatically as a new “point release” would be.