SemVer Sentry automatically detects any Pull Request changes which will break backwards comptatibility and let you know before you merge.
See a detailed breakdown of exactly which code is breaking backwards compatibility so you can change it or keep it.
Based on it's analysis, SemVer Sentry will suggest the next version number for your project for when the PR is merged.
Semantic Versioning (SemVer for short) is a very helpful convention that saves a lot of problems when it comes to managing dependencies, provided that it is done right. By following the SemVer conventions we can allow dependencies to upgrade if patches or new features come out, safe in the knowledge that nothing will break. It's a frustrating experience when a package claims to use SemVer but doesn't do it correctly; if you update a package that was supposed to be a bugfix but the maintainers actually let in a backward incompatible change then your code will probably break. Don't be that maintainer.
SemVer Sentry integrates with GitHub (more integrations coming soon) and runs an analysis of each Pull Request to your project. It will leave a comment in the Pull Request with the results, including details of any backwards incompatible changes if there are any and a suggested next version number to use should the Pull Request be merged.
SemVer Sentry is currently in private Beta so we haven't nailed down our pricing. Public projects will probably be free while private projects will have a cost.
SemVer Sentry currently only has support for PHP projects, but more languages will be coming soon. If you're interested in using SemVer Sentry with another language, get in touch using the form below!
Theme adapted from BlackTie.co