After some digging, I found the solution for #93.
With the change in gradle versions (#86), the generated metadata POM included a special marker, telling gradle to instead use the gradle module metadata, which does not include the dependency version numbers configured with the used dependency-management plugin. I therefore disabled the generation of said gradle module metadata files, so that the POM File is evaluated as expected.
After some digging, I found the solution for #93. With the change in gradle versions (#86), the generated metadata POM included a special marker, telling gradle to instead use the gradle module metadata, which does not include the dependency version numbers configured with the used dependency-management plugin. I therefore disabled the generation of said gradle module metadata files, so that the POM File is evaluated as expected.