Skip to content

ci: add canary dispatcher for canary-tested PRs (PILOT-162)#179

Open
hank-pilot wants to merge 1 commit into
mainfrom
hank/PILOT-162-canary-dispatcher-web4
Open

ci: add canary dispatcher for canary-tested PRs (PILOT-162)#179
hank-pilot wants to merge 1 commit into
mainfrom
hank/PILOT-162-canary-dispatcher-web4

Conversation

@hank-pilot
Copy link
Copy Markdown
Collaborator

PILOT-162 — Wire canary CI from web4

Copies the dispatcher template from pilot-protocol/pilot-canary/.github/templates/dispatcher.yml.

What it does

On every push/PR to any branch, dispatches a repository_dispatch event to pilot-protocol/pilot-canary with:

  • event_type: component-changed
  • component: web4
  • ref: <branch-name>

The canary build resolves web4 to this branch, using latest-stable for other components (rendezvous, updater, common).

Setup required

Add CANARY_DISPATCH_TOKEN secret to this repo (use matthew-pilot's PAT with repo + workflow scopes).

Copies the dispatcher template from pilot-protocol/pilot-canary.
On every push/PR, dispatches a repository_dispatch event to
pilot-canary's build-and-deploy.yml with component=web4.
This closes the CI gap where web4 changes aren't canary-tested.

Setup required: add CANARY_DISPATCH_TOKEN secret to this repo
(use matthew-pilot's PAT with repo+workflow scopes).
Comment on lines +29 to +45
runs-on: ubuntu-latest
steps:
- name: Dispatch repository_dispatch to pilot-canary
env:
GH_TOKEN: ${{ secrets.CANARY_DISPATCH_TOKEN }}
# CHANGE THIS to match your component name in pilot-canary's resolve step
COMPONENT: web4
REF: ${{ github.head_ref || github.ref_name }}
run: |
set -euo pipefail
echo "Dispatching: component=$COMPONENT ref=$REF"
gh api -X POST /repos/pilot-protocol/pilot-canary/dispatches \
-f event_type=component-changed \
-f client_payload[component]="$COMPONENT" \
-f client_payload[ref]="$REF" \
-f client_payload[source_repo]="${{ github.repository }}" \
-f client_payload[source_sha]="${{ github.sha }}"
@hank-pilot
Copy link
Copy Markdown
Collaborator Author

hank-pilot commented May 29, 2026

🤖 Hank — CI status

Classification: real
Run: https://github.com/TeoSlayer/pilotprotocol/actions/runs/26666511488
At commit: a90cfd7

The build/test failure is a genuine code defect:

FAIL	./pkg/registry/... [setup failed]
FAIL	./pkg/secure [setup failed]
pattern ./pkg/registry/...: lstat ./pkg/registry/: no such file or directory

@matthew-pilot — fix or comment.

Auto-classified at 2026-05-30T00:12:11Z. Re-runs on next push or check completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants