You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CI Node version matrix not applied – using default Node 20.x (Ubuntu) and 18.x (Windows) for all 6 runs.
Operating system and version: GitHub-hosted runners (ubuntu-latest, windows-latest)
Browser and version: N/A (CI-related)
Bug description:
The GitHub Actions workflow .github/workflows/npm.yml defines a matrix to test across Node versions 16.x, 17.x, and 18.x, but the setup-node step references env.node-version, which is not connected to the matrix.
As a result, the matrix is not being used, and the jobs are falling back to the default Node versions provided by GitHub runners.
For example:
✅ build (ubuntu-latest, 17.x) — succeeded but actually ran:
node: v20.19.0
npm: 10.8.2
Suggested fix:
In the workflow file, replace node-version: ${{ env.node-version }} with node-version: ${{ matrix.node-version }}, however, this will likely cause the workflow to fail.
The text was updated successfully, but these errors were encountered:
CI Node version matrix not applied – using default Node 20.x (Ubuntu) and 18.x (Windows) for all 6 runs.
ubuntu-latest
,windows-latest
)Bug description:
The GitHub Actions workflow
.github/workflows/npm.yml
defines a matrix to test across Node versions 16.x, 17.x, and 18.x, but thesetup-node
step referencesenv.node-version
, which is not connected to the matrix.As a result, the matrix is not being used, and the jobs are falling back to the default Node versions provided by GitHub runners.
For example:
✅
build (ubuntu-latest, 17.x)
— succeeded but actually ran:Suggested fix:
In the workflow file, replace
node-version: ${{ env.node-version }}
withnode-version: ${{ matrix.node-version }}
, however, this will likely cause the workflow to fail.The text was updated successfully, but these errors were encountered: