SonarQube cloud warns Node.js version 18 is not supported
Description
Environment
Potential Workaround
Checklist
hideActivity
David Crossley April 9, 2025 at 11:07 PM
Oh wow, i did not think to investigate that aspect. Glad that you found it.
But still, you should stop depending on the explicit v5.0.0 at ui-sonarcloud.yml#L65
Zak Burke April 9, 2025 at 6:10 PM
Thanks for the careful research, ! It looks like the real culprit is a too-strict dependency in stripes-smart-components' ui.yml file on v1.5 of our own workflow. That constraint holds us back on sonarsource/sonarcloud-github-action instead of allowing the migration to sonarsource/sonarqube-scan-action that was released in v1.9. Sorry for the noise.
David Crossley April 9, 2025 at 1:57 AM
The use of "Node20" that you refer to, is for the whole UI Workflow. The relevant piece is ui-sonarcloud.yml#L65 where your Workflow uses "SonarSource/sonarqube-scan-action@v5.0.0".
The relevant ticket is FOLIO-4190 where there was a need to migrate from the old "sonarsource/sonarcloud-github-action" to "sonarsource/sonarqube-scan-action". And your subsequent pull/77.
I indicated at FOLIO-4190 that we had already migrated for mod-reporting and all was working well. See go-sonarcloud.yml#L29 where we used "sonarsource/sonarqube-scan-action@v4".
Note that we still do use that "v4". (We have not yet found time to verify and upgrade to "v5".)
The recent Workflow mod-reporting run produced this
Sonar report -- there is no such warning about old Node.js there.
I am surpised that your team used "v5.0.0" explicit patch version (and still do). There could easily have been problems with an initial release. I would always wait for one or two subsequent releases before migrating.
Also, when ready, i would specify a "major version" only, i.e. "@v5" and let it resolve to most-recent. If that has troubles then go back to the working version, or temporarily specify an explicit patch version.
I am handing this ticket back to "Stripes Force" team for maintenance, as we discussed on FOLIO-4190.
Details
Assignee
UnassignedUnassignedReporter
Zak BurkeZak BurkePriority
TBDDevelopment Team
Stripes ForceTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Reporter
Zak BurkePriority
TBD
Summary: When analysing stripes-* PRs, SonarQube cloud whines about its Node.js version:
I would love to upgrade to a newer LTS version of Node.js, but I cannot figure out where this information is specified, and there is no link in the warning message to point me in the right direction. In our own GA environment, we explicitly ask for v20 (which we will soon update to v22 for Trillium) but sonar scans run on SonarQube’s environment.
This is not urgent from my point of view, though hearing that a version is unsupported suggests that this version will (soon?) be disabled. From that point of view it would be nice to get ahead of this before our hand is forced when this actively breaks.