fix!: Versioning via Version class instead of BigDecimals #2520
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.
Description
Replace usage of
BigDecimal
with a new classVersion
for database versioning. The current problem is that we store only major/minor versions insideBigDecimal
number, but ignore patch version.PR introduces a new class
Version
that stores major, minor and patch versions, and allows to check if one version covers another one.Type of Change
Please mark the relevant options with an "X":
Updates/remove existing public API methods: