Symptom
CI runs on PRs against main show a check named literally:
Cross-Platform (${{ matrix.os }}, Node ${{ matrix.node }}): skipping
The matrix interpolation never expanded. Observed consistently across PRs #751, #752, #753 (every recent CI run on this repo).
Hypothesis
A workflow YAML file has a matrix-strategy job whose name: interpolation uses incorrect syntax (${{ matrix.os }} would expand inside an if: or run: context, but name: might require a different shape) OR the matrix is being instantiated with an empty/missing values list, causing GitHub Actions to fall back to literal text.
Search
git grep '${{ matrix' .github/workflows/ | grep -i name…should locate the workflow. Likely one of: npm-publish.yml, ci-gate.yml, installer-smoke-matrix.yml.
Impact
Cosmetic — the job is consistently skipping, so it doesn't run anyway. But shows up in PR checks with the unexpanded literal, which is confusing for reviewers trying to read CI status.
Out of scope
Not blocking anything. Tracked here so it doesn't get forgotten.
Symptom
CI runs on PRs against
mainshow a check named literally:The matrix interpolation never expanded. Observed consistently across PRs #751, #752, #753 (every recent CI run on this repo).
Hypothesis
A workflow YAML file has a matrix-strategy job whose
name:interpolation uses incorrect syntax (${{ matrix.os }}would expand inside anif:orrun:context, butname:might require a different shape) OR the matrix is being instantiated with an empty/missing values list, causing GitHub Actions to fall back to literal text.Search
…should locate the workflow. Likely one of:
npm-publish.yml,ci-gate.yml,installer-smoke-matrix.yml.Impact
Cosmetic — the job is consistently
skipping, so it doesn't run anyway. But shows up in PR checks with the unexpanded literal, which is confusing for reviewers trying to read CI status.Out of scope
Not blocking anything. Tracked here so it doesn't get forgotten.