Hi everyone!
My name is Mikhail Polivakha, and I am the technical lead of the Axelix project. We recently passed the mark of 10,000 downloads per month . We build a tool for working with Spring applications ourselves, so release cycles, version support and dependency upgrades are not abstract theory for me. I run into them both as a Spring user and as a developer of an Open Source project.
I want to start with a situation that, I think, is familiar to many. The release is already planned, the feature is written, the tests are green, the build is assembled. All that's left is to run the last pipeline and roll out the changes. And then, at the SCA step, everything turns red: a vulnerability has been found in one of the dependencies.
Well, it happens. We'll just bump the patch version, pick up the fix and move on. That's what patch releases are for, right?
You open Maven Central, look at your Spring Boot line, and the next number isn't there.…