ci: skip smart e2e ai selection for cherry-pick PRs targeting release branch#28331
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: What changed:
Impact on app: None — this is purely CI infrastructure. Why run any tests at all: Since this is a critical CI infrastructure file that controls the test selection pipeline itself, running a representative set of tests validates that the action still works correctly for the normal (non-release-branch) code path. A small but representative set of smoke tests across core areas is appropriate. Why not run all tags: The app code is completely unchanged. Running all tags would be excessive for a CI description/logic-only change. The selected tags (SmokeAccounts, SmokeConfirmations, SmokeWalletPlatform, SmokeNetworkAbstractions) provide broad coverage across core wallet functionality to validate the pipeline works. No performance tests needed: No app code, rendering, data loading, or performance-sensitive paths were modified. Performance Test Selection: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #28331 +/- ##
========================================
Coverage 82.66% 82.67%
========================================
Files 4866 4869 +3
Lines 126134 126239 +105
Branches 28268 28293 +25
========================================
+ Hits 104273 104367 +94
- Misses 14660 14666 +6
- Partials 7201 7206 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|



Description
This PR is to make release cherry-pick PRs execute the full smoke e2e instead of a reduced tag set chosen by ai.
On main, iterating quickly with a risk-scored subset is a reasonable tradeoff: we accept some residual risk in exchange for speed and we will catch more in follow-up PRs. A PR into release/* is effectively “this build is a candidate to ship.”
Smart selection saves CI time on high-volume main development. Release cherry-picks are low volume and high impact, and we cannot afford to merge cherry-pick that breaks the CI on release branch due to release urgency.
Changelog
CHANGELOG entry: null
Related issues
Fixes: https://consensyssoftware.atlassian.net/browse/INFRA-3464
Manual testing steps
cherry-pick PRs should run all e2e tests
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Medium Risk
Changes CI behavior for release-branch PRs by bypassing AI selection and forcing full E2E runs, which can affect build time and which tests execute. Logic is localized to a single composite action and does not touch product code.
Overview
Updates the
smart-e2e-selectioncomposite action to detect PRs targetingrelease/*and skip the AI-based E2E test selection in that case.For
release/*PRs it now forces full E2E execution by settingforce_run=true(andai_confidence=100), and it avoids the checkout/dependency install steps used only for AI analysis; copy updates output/input descriptions to reflect the new behavior.Written by Cursor Bugbot for commit 122d8e6. This will update automatically on new commits. Configure here.