No, unfortunately it isn't. This is a common restriction for complex file types, where changes in the tool can cause many changes throughout the project file. You could export to JSON and version that, but conflicts may be difficult to resolve. Another potential solution is to have a master project, give a copy to animators to create animations, then merge the animations back into the master project using Import Data. Note that currently to import an animation the target skeleton must have all the bones, slots, attachments, etc that the animation you are importing references. This means if you add bones, slots, attachments, etc in the master project, you will need to give the animators a new copy.

This has happened to us quite a few times and its annoying. Luckily the changes where small, or where able to be resolved with the skeleton merge tool #plug