You want to explore the newest Spine features.

You want to use the newest Spine features and don't mind waiting until the runtimes have been updated.

You are exporting images or video, so lacking runtime support doesn't matter to you.

Here are a few reasons you may want to use a beta release: Also, exports from a beta version may not yet be supported by all Spine Runtimes. For example, 4.0.73-beta for the Spine editor and 4.0-beta for the Spine Runtimes.īeta versions let you use the latest new features, but the Spine editor may crash occasionally or have features that are not completely implemented. Beta releasesĪ beta release is any that ends with -beta. Updates to stable releases are mainly to fix bugs. We don't make risky changes to stable releases in order to reduce the chance that new problems are introduced. For example, 3.8.99 for the Spine editor and 3.8 for the Spine Runtimes. Git commits to a branch are used instead of patch version numbers.Ī stable release is any that doesn't end with -beta. Git branches are used for each version of the Spine Runtimes. The source code for the Spine Runtimes is provided in the Spine Runtimes GitHub repository.

The Spine Runtimes version numbers use the format major.minor. The changelog archive provides a list of all Spine editor versions we have ever released. When only the patch version number changes, it means that we have fixed bugs or have done minor improvements and it is safe for you to update. When the major or minor version numbers change, it indicates a significant difference and caution should be used before updating to the newer version. Spine editor version numbers use the format. Keeping track of your Spine editor and Spine Runtimes versions is an important part to using Spine.

Esoteric software spine api