You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the Lottie supports an SPM I think it's safe to say that we should follow its rules. One of them relates to the versioning of libraries. In the documentation we can find below quote:
A package version consists of three integers separated by periods, for example 1.0.0. It must conform to the semantic versioning standard in order to ensure that your package behaves in a predictable manner once developers update their package dependency to a newer version.
Latest release (3.5.0) includes #1420, which is not backward-compatible.
I assume that the dangers of such a release are clear, but if you need more information regarding this, just let me know :)
Because of the above, I just wanted to start the discussion about sticking to semver convention.
The text was updated successfully, but these errors were encountered:
Hey there!
Since the Lottie supports an SPM I think it's safe to say that we should follow its rules. One of them relates to the versioning of libraries. In the documentation we can find below quote:
Latest release (3.5.0) includes #1420, which is not backward-compatible.
I assume that the dangers of such a release are clear, but if you need more information regarding this, just let me know :)
Because of the above, I just wanted to start the discussion about sticking to semver convention.
The text was updated successfully, but these errors were encountered: