POC Compute next release version from the assessed compatibility level #21
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
julienrf
force-pushed
the
semver-release-version
branch
from
971e1f6
to
5989d44
Compare
julienrf
force-pushed
the
semver-release-version
branch
from
5989d44
to
be1559f
Compare
3 tasks
rtyley
force-pushed
the
main
branch
14 times, most recently
from
2d0e71c
to
284e034
Compare
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.
What does this change?
This PR uses
sbt-version-policyto assess the compatibility level of the project modules and bump the version accordingly during the release process. For instance, if one of the modules introduced a binary incompatibility, the release process will automatically bump the major version, thus conforming to Semantic Versioning.How to test
How can we measure success?
Have we considered potential risks?