Skip to content
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

Consider switching to semantic versioning #162

Open
noisycomputation opened this issue Jun 6, 2020 · 0 comments
Open

Consider switching to semantic versioning #162

noisycomputation opened this issue Jun 6, 2020 · 0 comments

Comments

@noisycomputation
Copy link

It looks like the version bump from 1.5 to 1.6 was an API-breaking change. I had been pinned to 1, but things stopped working when I updated to 1.6.

Could you consider moving to semantic versioning?

Is there a reason you don't git tag your version bumps? Having to look at the commit history is not the most efficient way of figuring out what happened when.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant