IndieDoroid a écritThe concern is more about having to re-export everything by hand.
It doesn't have to be done manually. You can and likely should automate it, which will be less work to export and less chance that something is exported incorrectly or is forgotten.
IndieDoroid a écritI would be crushed if I had to re-export everything when I'm days away from launch or a major milestone deliverable to my publisher.
You should never update a runtime or editor version without first being sure it works correctly for you and certainly never before a launch! Updating any dependency is a significant event and should be approached with caution.
IndieDoroid a écritwould it be ok to ask for some kind of batch project export function inside Spine?
You can have multiple skeletons in one project, then you would only need to export one project.
SoulKarl a écrituntil now this has never once come up.
Every single release that changes the binary format has caused exports from older versions to fail to be read by the newer release. The JSON format is much more resilient to changes. Often newer versions can load older JSON, but that is not guaranteed and many times in the past a re-export has been required.