#updatePackageMethodIn:sourceVersion: does not update nested project version when performed with a non-baseline sourceVersion

Well, it's all in the title :)

I have noticed this thing recently, when I generate a new version from another regular version (i.e., not a baseline), version numbers for nested projects are not updated with the current version of projects. This makes the new version outdated.

Is this a known bug?

--
 Simon