When exactly is publishCmd run?

I would like to run a command that uses the newly updated package.json version and write it into a file that is added to git to be included as part of the release commit, is it possible to do so with exec?

My use case is that I'm building a hybrid app where semantic-release would bump the package.json version, I would then like to use the new package.json version to update the native android & ios versions based on that and push that to git as part of the release commit, is that something I can accomplish with exec, or do I manually need to trigger my script after release as a separate commit?

I tried setting that as part of the publishCmd but it didn't work, it seems to be run either too early before the new package.json version is set or too late after the commit has already been made
PS: npmPublish is set to false

Start by tracing when publishCmd runs relative to the package.json version update and release commit, using the issue's semantic-release exec workflow as the scope. Confirm whether npmPublish=false changes that ordering, then document the supported timing and whether the requested Android and iOS version update can be included in the release commit.