chore: upgrade to Spring Boot 3 #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Spring Boot 3 made some changes to the way a library, such as this one, notifies Spring Boot that it wants to be autoconfigured. [Details of this change are in the release notes of version 2.7][1]. With this commit, a new versioning system for this package is proposed: `<Spring Boot version>-<tradition semantic versioning>`. For example, `3-1.0.2`. Why? The problem with only semantic versioning _and_ following Spring releases (especially those with breaking changes) is, that it becomes unclear when to update to a new major version. Should we do it when this library introduces a breaking change? Or when Spring Boot does? To solve this, the version now consists of a leading digit, indicating the Spring Boot version that this version works with, followed by a semantic version of the library itself. So, we now have `2-1.0.2`, working with Spring Boot 2, alongside `3-1.0.2`, which works with Spring Boot 3. When a breaking change is made to this library, we would signal that by bumping the versions to `2-2.0.0` and `3-2.0.0`, respectively. [1]: <https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.7-Release-Notes#changes-to-auto-configuration>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spring Boot 3 made some changes to the way a library, such as this one,
notifies Spring Boot that it wants to be autoconfigured.
Details of this change are in the release notes of version 2.7.
With this commit, a new versioning system for this package is proposed:
<Spring Boot version>-<tradition semantic versioning>. For example,3-1.0.2. Why? The problem with only semantic versioning andfollowing Spring releases (especially those with breaking changes) is,
that it becomes unclear when to update to a new major version. Should we
do it when this library introduces a breaking change? Or when Spring
Boot does? To solve this, the version now consists of a leading digit,
indicating the Spring Boot version that this version works with,
followed by a semantic version of the library itself.
So, we now have
2-1.0.2, working with Spring Boot 2, alongside3-1.0.2, which works with Spring Boot 3. When a breaking change ismade to this library, we would signal that by bumping the versions to
2-2.0.0and3-2.0.0, respectively.