If that is the problem, it occurs because the behavior of transform constraint changed in a subtle way. We expected that few projects rely on the old behavior and the fix was necessary to make transform constraint work correctly.
To put it another way, transform constraint didn't work correctly in a very specific configuration. When we fixed that, projects that depended on the old, incorrect behavior will need to be fixed manually.
Unfortunately I don't believe it is possible to fix this automatically. I hope that few of your projects have this problem! This is only the second time it has been reported since the change was made in 4.2.60-beta.
