Hi,
I notice the spine-unity runtime includes a package.json and the appropriate asmdefs and can thus be loaded as a UPM package. However, due to the missing spine-csharp it however cannot be used out of the box.
It seems safe to assume the intended workflow is to fork the repository and add spine-csharp into its folder before grabbing the package via the package manager. While this does have the advantage of giving us free reign to modify the source, this doesn't seem like a preferable choice for general use.
Now, our first thought at this point was to at least pull spine-csharp into its folder as a subtree (or submodule) to simplify ugprading. However, could this not be taken further by having the official repository itself include spine-csharp as a subtree or -module?
As far as dependency management goes, there's no going back from UPM and being able to add the base package into the project as easily as the extensions would definitely be a big plus in Spine's favour as far as our studio is concerned.
edit: in hindsight, this might've been a better fit for the Unity subforum. Feel free to move it if you feel that way.
edit 2: I notice this has been discussed before around one year ago and the main problem at the time seems to have been the runtime repository's stucture not being directly compatible with UPM. Since then Unity added support for directly referencing repository subdirectories as package roots. This solved most of the issue with your runtimes being in a monorepo, leaving just the issue of the missing spine-csharp.
