Semantic Gradle: How to Publish Artifacts Calmly and Confidently

Did you have to develop a library project and publish artifacts at one point? We had to when we started to have our own design system and some reusable parts of our applications. At first everyone was happy, but later on it turned out that it's quite exhausting to avoid breaking other projects by making some nonchalant changes. Eventually we got tired of fighting breaking changes manually and started wishing to have so magic: so that the versions increment by themselves and also indicate whether any breaking changes have taken place.

In my presentation I will tell you how we taught Gradle to analyze API changes and increment artifact versions automatically while adhering to semantic versioning. In addition, we will learn some tricks useful for writing Gradle plugins. The presentation will be useful not only to those who develops libraries and wants to implement a similar solution, but also those who want to learn writing Gradle plugins.