Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Follow semantic versioning #1781

Closed
kkiermasz opened this issue Oct 18, 2022 · 0 comments
Closed

Follow semantic versioning #1781

kkiermasz opened this issue Oct 18, 2022 · 0 comments

Comments

@kkiermasz
Copy link

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:

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.

@airbnb airbnb locked and limited conversation to collaborators Oct 18, 2022
@calda calda converted this issue into discussion #1782 Oct 18, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant