Support for full semantic versioning in LSP artifacts #329
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
breedloj
force-pushed
the
breedloj/semanticVersioning
branch
from
db107b4 to
8fee1ac
Compare
nborges-aws
approved these changes
Jan 24, 2025
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.
Description of changes:
Adds support for extended semantic versioning, including additional labels for pre-release such as
2.0.1-rc.1, to the LSP artifact fetcher. This support utilizes themaven-artifactlibrary which includes a number of constructs for managing artifact versions.Precedence is given to non labeled versions, or to the latest logic label, for example:
1.8.3-beta.1 < 1.8.3-rc.1 < 1.8.3-rc.2.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.