ci: run E2E tests on feature PRs that touch web-relevant paths

[FSM1]

Summary

• The release gate's "Verify E2E Passed" check was auto-passing for non-release PRs with "Not a release PR — E2E gate not applicable", allowing PRs to merge without E2E verification
• Now detects web-relevant path changes (apps/web/, apps/api/, packages/, tests/web-e2e/) on all PRs
• For feature PRs with web changes: runs E2E inline via workflow_call to e2e.yml and gates on the result
• Release PR behavior unchanged (still polls for E2E on main)

How it works

1. detect-changes job now runs a web-path check on all PRs (not just release PRs)
2. New run-web-e2e job calls e2e.yml via workflow_call when web paths are changed and it's not a release PR
3. verify-e2e checks the run-web-e2e result for feature PRs instead of auto-passing

Test plan

• This PR itself should trigger the new path: it changes .github/workflows/ which doesn't match web patterns, so E2E should skip with "No web-relevant changes"
• A PR touching tests/web-e2e/ or apps/web/ should trigger the full E2E run before merge is allowed
• Release PRs should continue to use the existing polling behavior

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced release workflow to detect web-related changes and conditionally run end-to-end tests only when necessary, improving CI/CD efficiency and reducing redundant test execution on non-web modifications.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

The pull request modifies the release-gate.yml GitHub Actions workflow to detect web-relevant changes across specific directory paths and conditionally execute a web E2E workflow. It adds change detection output, introduces a new job to run the E2E workflow when changes are detected, and updates the verification job to depend on and validate the E2E results.

Changes

Cohort / File(s)

Summary

Workflow Change Detection & E2E Gating .github/workflows/release-gate.yml

Added web_changed output to detect-changes job that queries PR file lists via gh api and matches against apps/web/, apps/api/, packages/, and tests/web-e2e/ directories. Introduced run-web-e2e job that calls the reusable e2e.yml workflow for non-release-please PRs when web changes are detected. Updated verify-e2e job to depend on run-web-e2e and conditionally fail if E2E failed when changes detected, or skip when no changes detected.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• chore(ci): make Verify E2E Passed a required check #264: Modifies the same detect-changes and verify-e2e logic in release-gate.yml, directly adjusting change-detection outputs and E2E job gating behavior.
• chore(ci): run full E2E suites in tag-staging workflow #261: Makes the e2e.yml workflow callable via workflow_call and adds ref handling, enabling the conditional invocation pattern introduced in this PR.
• fix(ci): poll for E2E completion in release gate #252: Modifies release-gate.yml E2E gating to detect affected platforms and coordinate platform-specific E2E execution, overlapping with this PR's change-detection and gating approach.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding E2E test execution for feature PRs that modify web-relevant code paths, which is exactly what the changeset implements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-gate-e2e-for-feature-prs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[FSM1]

Closing — this addresses the wrong problem. The real issue is the release gate not re-triggering when new code lands on main.