Maya 2024.0.1 didn't update the API version info?

[david.oberst]

Maya 2024.0.1 (on Windows) reports as "2024.0.1" on the splash screen, the Help/About dialog, and in the values returned by maya.cmds.about() for majorVersion/minorVersion/patchVersion (patchVersion is "1").  However, maya.cmds.about(apiVersion=True) and maya.api.OpenMaya.MGlobal.apiVersion() returns 20240000, NOT 20240001 as might be expected.

Did Autodesk forget to bump the API versioning with the 2024.0.1 patch release?  Or is the API version considered unchanged, at 20240000, and separate from the "app version"?  That would be a bit unfortunate, as there seems to be no way to get the same info that is feeding about(), using the OpenMaya interface.  Using maya.cmds.about() from mayapy requires maya.standalone.initialize() to be called, which OpenMaya does not.

[brentmc]

It looks like the API version was not bumped but it does not matter since the API was unchanged from 2024.0.

2024.0.1 was a patch release that primarily targeted issues affecting Maya when running the Japanese or Chinese versions.
https://help.autodesk.com/view/MAYAUL/2024/ENU/?guid=MAYA_RELEASENOTES_2024_0_1_RELEASE_NOTES_HTML

[david.oberst]

It does make a difference, if the "api version" and the "application version" are intentionally two different concepts.  There appears to be no way to get the full "application version" info through the OpenMaya APIs?  MGlobal.apiVersion() returns the "api version", and MGlobal.mayaVersion() returns a string of the major version, like "2020".  I don't know if I'm missing another way to get the application version, or if the C OpenMaya API has one that isn't exposed via Python?  

I'm not sure how the maya.cmds.about() implementation gets the majorVersion/minorVersion/patchVersion values.  For my purposes (writing a tiny mayapy script to output the full installed application version number), about() has two drawbacks.  Those options don't seem to be available before Maya 2020, and worse, require maya.standalone.initiialize() to be called first.  At a minimum, it looks like I'll have to wrap something around that latter call to redirect standard output temporarily, since initialization may spit out text to stdout.

[brentmc]

They are meant to be in sync but now that the patch is out it is too late to fix this.

I'll bring this up internally as something we can look at improving.