Skip to content

ci(fleet): make browser release evidence manually dispatched #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devswha merged 1 commit into from
Aug 29, 2026
Merged

ci(fleet): make browser release evidence manually dispatched #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ on:
- '**.md'
- 'docs/**'
- '.github/ISSUE_TEMPLATE/**'
workflow_dispatch:

permissions:
contents: read
Expand Down Expand Up @@ -117,10 +118,11 @@ jobs:

fleet-release:
name: Fleet release evidence
# Release-grade browser/desktop QA runs after merge on main; per-PR runners
# starve the fixture startup budgets without proving anything the required
# Verify gates do not already cover.
if: github.event_name == 'push'
# Release-grade browser/desktop QA requires a warm dedicated host; CI runners
# starve the fixture startup budgets with high variance. Run it manually (the
# owner's verified local cua:release flow remains the release gate) and keep
# automatic CI on the verify and bundle contracts.
if: github.event_name == 'workflow_dispatch'
needs: [verify, bundle]
runs-on: ubuntu-22.04
timeout-minutes: 60
Expand Down
Loading