CI: always run the cross-browser release matrix on main again

Merged
BI
1mo ago
+50-102

User description

Owner-approved follow-up to #3524.

#3524 added a "matrix" tree proof that let a push to main skip the Firefox/WebKit/iPhone release-browser-matrix when a green full-suite workflow_dispatch run on the merged PR head had tested the same tree. This restores the previous behaviour: on main the matrix always runs when UI, perf or the lockfile changed (it never runs on a PR, so main is the only place it guards every merge).

Changes:

  • .github/workflows/ci.yml: drop the tree_proven_matrix output and its condition on release-browser-matrix.
  • tests/ci-main-tree-proof.test.ts: assert the matrix has no tree-proof gate.
  • docs/ci-operations.md: say the proven-tree skip never skips the matrix.

The parallel start (matrix alongside Production UI) and the 4-way Firefox/WebKit split from #3524 are unchanged. scripts/ci-main-tree-proof.mjs still computes a matrix value that nothing reads now; it is harmless, and removing it is left for a separate cleanup to keep this change small.

Tests: tests/ci-*.test.ts and the workflow tests pass locally (514).

Summary by cubic

Restores the main behavior where the Firefox/WebKit/iPhone release-browser-matrix always runs when UI, perf, or the lockfile changed, removing the tree-proof gate from #3524 that let a green full-suite dispatch run on the merged PR head skip it.

  • Removes the tree_proven_matrix output and its condition on the matrix job in .github/workflows/ci.yml.
  • scripts/ci-main-tree-proof.mjs drops the dispatch-run lookup, no longer emits a matrix output, and never lists the matrix in the step summary; it proves skips only for coverage, UI, and Lighthouse.
  • Updates the wiring tests and docs/ci-operations.md to assert the matrix has no tree-proof gate.
  • The parallel start and 4-way Firefox/WebKit split from #3524 are unchanged.

CodeAnt-AI Description

Always run cross-browser release tests for qualifying main changes

What Changed

  • Pushes to main that change UI, performance inputs, or the lockfile always run the Firefox/WebKit release matrix.
  • Tree-proof checks can still skip proven coverage, UI, and Lighthouse jobs, but no longer look for a dispatch run to skip the release matrix.
  • CI summaries no longer report the release matrix as skipped by tree proof.

Impact

✅ Cross-browser checks on every qualifying main push
✅ No dispatch run needed to validate merged browser changes
✅ Accurate CI skip summaries

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.