Skip to content

ci(live-drift): route failures to a pinned issue and run after migration pushes (#316 phase 0)#1939

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
BigSimmo merged 3 commits into from
Aug 14, 2026
+12 −9
Merged

ci(live-drift): route failures to a pinned issue and run after migration pushes (#316 phase 0) #1939

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
61b5368
ci(live-drift): route failures to a pinned issue and run after migrat…
claude Aug 14, 2026
ca3cd83
docs(ledger): record live-drift routing review (PR #1939)
claude Aug 14, 2026
61751bf
Merge main and capture migration-history failures
BigSimmo Aug 14, 2026
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
21 changes: 12 additions & 9 deletions .github/workflows/live-drift.yml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -74,26 +74,29 @@ jobs:
set -o pipefail
npm run check:drift 2>&1 | tee drift-output.txt

- name: Capture drift findings
- name: Align migration history for Supabase Preview
run: |
set -o pipefail
npm run check:migration-history 2>&1 | tee migration-history-output.txt

- name: Capture drift and migration-history findings
id: findings
if: always()
run: |
# Line shapes come from scripts/check-drift.ts: the manifest/compared
# context lines, the "! [category] kind key" unexpected-drift findings,
# and the "? [category]" stale allowlist entries. Absent when the run
# died before the comparison (missing secret, identity guard); the
# routing job says so rather than implying a clean result.
# Keep a migration-history failure visible rather than publishing a
# successful drift result as the explanation for the failed job.
{
echo "findings<<LIVE_DRIFT_FINDINGS_EOF"
if [ -f drift-output.txt ]; then
grep -E '^(Drift manifest:|Compared |UNEXPECTED DRIFT| ! \[| \? \[)' drift-output.txt | head -80 || true
fi
if [ -f migration-history-output.txt ]; then
echo "Migration-history check output:"
tail -80 migration-history-output.txt
fi
echo "LIVE_DRIFT_FINDINGS_EOF"
} >> "$GITHUB_OUTPUT"

- name: Align migration history for Supabase Preview
run: npm run check:migration-history

# Split out so issues: write is scoped to a job that never installs or executes
# repository code — the drift job above keeps contents: read only.
drift-routing:
Expand Down
Loading