bklooster написал
The first problem was fixed by the runtime update (thanks).
Glad to hear, thanks for checking.
Regarding the second issue: sorry to hear that it still persists after the update. It's unfortunate that the Unity Perforce integration checks out the prefab file, just to write the same file content to it. Perhaps your could add a "Revert if unchanged" call automatically afterwards?
After reading your original posting again, I noticed that your problem was just with the build automation (during pre- and post build steps) and not with normal workflow. If you only need to prevent this problem, you could theoretically get away with "best of both worlds" at the cost of increased build-size by just disabling HAS_ON_POSTPROCESS_PREFAB in the SpineBuildProcessor.cs file. This way you should still get previews, it's just that the generated meshes are added to your build size, which could be OK for intermediate test builds.
