ci: pin @sonar/scan to v4.4.0#2677
Merged
Merged
Conversation
aryamohanan
force-pushed
the
ci-sonar-scan
branch
from
July 27, 2026 06:51
045b609 to
9a5cfd6
Compare
kirrg001
approved these changes
Jul 27, 2026
aryamohanan
marked this pull request as ready for review
July 27, 2026 09:27
abhilash-sivan
approved these changes
Jul 27, 2026
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
3 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.
The latest @sonar/scan v5.0.0 introduces breaking changes:
Requires Node.js 22.12.0+ (previously Node.js 18+ for v4).
Removes the deprecated sonar and sonar-scanner CLI aliases in favour of
sonar-scanner-npm.This PR pins @sonar/scan to v4.4.0 until the CI pipeline is updated to use the new CLI and meets the new Node.js requirement.
see: https://github.com/SonarSource/sonar-scanner-npm/releases/tag/5.0.0