SCANJLIB-304 Update tested SQS versions and Java version used by the CI#280
Merged
SCANJLIB-304 Update tested SQS versions and Java version used by the CI#280
Conversation
hashicorp-vault-sonar-prod
bot
changed the title
ericg138
force-pushed
the
eg/update-ci-java
branch
from
bafe43c to
b5db0be
Compare
ericg138
changed the title
henryju
approved these changes
Jan 30, 2026
Member
henryju
left a comment
henryju
left a comment
There was a problem hiding this comment.
In a perfect world, would have been nice to keep testing with Java 17, for example on the LATEST_RELEASE[2025.1] axis.
ITs running the latest SQS release require Java 21
ericg138
force-pushed
the
eg/update-ci-java
branch
from
b5db0be to
e150656
Compare
|
Contributor
Author
Done! 
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ITs running the latest SQS release require Java 21
Please be aware that we are not actively looking for feature contributions. The truth is that it's extremely difficult for someone outside SonarSource to comply with our roadmap and expectations. Therefore, we typically only accept minor cosmetic changes and typo fixes. If you would like to see a new feature, please create a new thread in the forum "Suggest new features".
With that in mind, if you would like to submit a code contribution, make sure that you adhere to the following guidelines and all tests are passing:
We will try to give you feedback on your contribution as quickly as possible.
Thank You!
The SonarSource Team