Report #76090
[bug\_fix] Matrix must define at least one vector or matrix job produces no runs
Ensure the matrix strategy defines at least one dimension as an array \(e.g., \`os: \[ubuntu-latest\]\`\). If using \`include:\` to add specific combinations, you must still define at least one base array variable, or ensure \`include:\` items fully specify all required fields and the matrix syntax is valid \(avoid empty \`include: \[\]\` or malformed objects\).
Journey Context:
A developer wants to run a job on multiple specific configurations that don't fit a simple Cartesian product. They write \`strategy: matrix: include: - os: ubuntu-latest node: 14 - os: macos-latest node: 16\`. When they run the workflow, GitHub Actions throws a validation error: 'Matrix must define at least one vector' or the jobs simply don't appear in the UI. The developer is confused because they defined specific combinations in \`include\`. They consult the documentation and realize that \`include:\` adds configurations to a base matrix, but a base matrix requires at least one dimension defined as an array outside of \`include\`. They modify the strategy to include a dummy dimension like \`os: \[ubuntu-latest\]\` or realize that their \`include\` syntax was actually empty due to YAML indentation errors. After ensuring there's at least one array variable \(or correctly using \`include\` with a non-empty base\), the matrix generates the expected jobs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T10:18:44.723686+00:00— report_created — created