ci: fix Node 20 deprecation warning in GitHub Actions#89
Merged
Conversation
qarlosh
requested changes
Jul 2, 2026
qarlosh
left a comment
There was a problem hiding this comment.
it seems that these versions (actions/checkout@v4 and actions/setup-python@v5) still use Node 20. checkout needs at least v5. I didn't check setup-python.
GitHub Actions runners are dropping Node 20 support, forcing actions pinned to it onto Node 24 with a deprecation warning. Bump actions/checkout to v7 and actions/setup-python to v6 in the build and deploy workflows to versions that target current Node natively. Part of LITE-33583.
9f607fd to
1b5cfe2
Compare
The SonarScanner (sonarcloud-github-action) is deprecated in favour of sonarqube-scan-action, and its internals still pull actions/cache@v4, which targets the now-deprecated Node 20 runtime. Switch to SonarSource/sonarqube-scan-action@v8 (runs on Node 24), setting SONAR_HOST_URL to https://sonarcloud.io since the generic scan action has no SonarCloud default; projectKey/organization stay in sonar-project.properties. Also bump actions/github-script v6 (Node 16) to v9 (Node 24) in deploy.yml, the remaining action on a deprecated runtime.
|
qarlosh
approved these changes
Jul 2, 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
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.
Summary
GitHub Actions runners are dropping Node 20 support, so actions still pinned to it are being force-run on Node 24 with a deprecation warning:
This branch bumps every affected action to a current major version that targets the required Node runtime natively, and replaces the deprecated SonarScanner action.
Node runtime bumps
actions/checkoutv3 → v7 (build.yml,deploy.yml)actions/setup-pythonv4 → v6 (build.yml,deploy.yml)actions/github-scriptv6 → v9 (deploy.yml) — v6 runs on Node 16, v9 on Node 24SonarCloud action replacement
SonarSource/sonarcloud-github-action@master→SonarSource/sonarqube-scan-action@v8(build.yml)sonarcloud-github-actionis deprecated in favour ofsonarqube-scan-action, and its internals still pullactions/cache@v4(Node 20), which is the source of the remaining cache deprecation warning. The replacement runs on Node 24. AddedSONAR_HOST_URL: https://sonarcloud.iosince the generic scan action has no SonarCloud default;projectKey/organizationalready live insonar-project.properties.Notes
@master-pinnedjakejarvis/wait-actionandsonarsource/sonarqube-quality-gate-actioninbuild.ymlare left untouched — they float already and don't emit the deprecation warning.Ref: LITE-33583