Yes, you assume correctly. The unitypackage is released manually with compatible combinations of spine-csharp and spine-unity only.
After a while means you start the game, the game runs for a while and then freezes.
So I assume you mean your game freezes both in the Unity Editor after entering play mode after some time as well as in the built executable, right?
Extracting reproduction project would probably be very time-consuming in this case.
That is why I was asking if there is any possible visible change in the code above that could be causing the problem.
Showing us the code changes that trigger your issue helps a bit, but the changes are there for a reason. In this case to fix issues when adding animations without advancing time but still triggering an update call (AnimationState.Update). Previously this could lead to a stack overflow, which is fixed by the above changes.
Unfortunately the relevant other part is your project setup and code which triggers your issue. I'm afraid we can't fix the issue without being able to reproduce it or understand what you are doing. We would love to fix any hidden issues or prevent potential problems, so if you could sometime in the future try to strip your problematic project down to just the problematic parts, that would be a great help.
