getsentry/sentry-capacitor

Use Semver for versioning

markieo1 opened this issue · 2 comments

All of the Sentry packages follow Semver.

This is one, doesn't follow Semver. Which means we do not exactly know if there are breakings changes by upgrading. Only by looking at the release notes we might know.

My suggestion is to adjust the versioning to follow Semver, just like all the other Sentry packages do.

Thanks for opening this issue!

We alter the the major number here once breakchanges are introduced that impact the end user, the minor for new features and the patch if the version only includes bug fixes

Feel free to reply if you have any questions