In case any readers are not aware, we do maintain a migration guide for each version:
Unfortunately – automating upgrades with each version is not likely to be an easy task. I don’t think maintainers are able to make such a time commitment, which would come at the cost of library development.
Agreed that links back and forth would be worthwhile!
The harder part is that it isn’t easy to write a script with enough context to do these migrations correctly. I’ve migrated 100+ examples in the three.js codebase, and there’s a certain amount of context required. Renaming a property is easy. But knowing how a texture is being used, and what kind of data it contains, determines what color space it should be given. If your textures were not already tagged with color space information — as many were not — then a script has no practical way to infer that. The color space data contained in PNG and JPEG files is very unreliable.