LTRAC-2170: ci - Skip Regression Tests for merge queue builds

[jorgemoya]

Linear: LTRAC-2170

What/Why?

Vercel deploys the merge queue's temporary branch (gh-readonly-queue/canary/...) as a Preview, and that deployment starts a Regression Tests run before the commit lands on canary. The commit isn't on canary yet, so the run treats it as a PR. A few minutes later, canary's own Production deployment of the same commit starts the real run, and because both share a concurrency group, it cancels the first. Every canary commit then shows a set of cancelled Unlighthouse audits next to the successful ones, and each merge wastes about 5 minutes on four runners.

This was seen on the merge of #3259: run 37051672166 (queue build, cancelled) and run 37052249183 (Production, passed).

The Find Baseline Deployment step now skips a deployment whose commit is the head of a gh-readonly-queue/* branch.

• Guard: the skip only applies outside the base branch's own environment, so canary's Production run can never be skipped, even if the queue branch hasn't been deleted yet.
• Late queue builds: if the queue build's deployment finishes after its branch is gone, the existing rule already skips it, because a Preview of a commit already on canary is ignored.

Testing

• Confirmed git ls-remote patterns match across slashes: dependabot/* matched dependabot/npm_and_yarn/diff-4.0.4.
• Tested the skip condition on four cases:
  • Queue build: skipped.
  • Production deployment while the queue branch still exists: runs.
  • PR preview with no queue: runs.
  • PR preview with other queue heads: runs.
• Dry-ran the full detection step against real commits (canary push, Preview of a canary commit, PR commit). All behave as before.
• Not tested against a live queue build, because none was running. The first canary merge after this lands should show the queue build's run ending at Find Baseline Deployment with a "Merge queue build" notice, and only one full run on the canary commit.

Migration

None.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2cf33ce

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
catalyst	Ready	Preview	Oct 2, 2026 8:24pm UTC