Repository navigation
fix(wizard-ci): fix the known-broken CI legs and log links - #4326
Merged
Merged
Conversation
- Get job ID: page through every job and match the name exactly. A full run has 51 jobs, past the API's first page of 30, so many rows got an empty logs link, and next-stripe matched next-stripe-declined. - Retry createCommitOnBranch on 5xx. After a 504, check the branch first: if GitHub already wrote the commit, use it instead of resending. - Use a restricted-key shape for the Stripe fixture. The warehouse skill makes the agent refuse an sk_ key, so no Stripe source was created. - Seeded legs: pass the warehouse program's askAnswers through E2E_ANSWERS_FILE, and skip "report written" when the program declares no report file. - Run the api-commits tests in Checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gewenyu99
marked this pull request as ready for review
October 5, 2026 09:53
edwinyjlim
approved these changes
Oct 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Wizard CI runs on release PRs fail the same way every time, from causes that are cheap to fix.
Changes
next-stripelinked tonext-stripe-declined. The step now pages through all jobs and matcheswizard-ci (<app>)exactly.createCommitOnBranchnow retries 5xx up to 3 times. After each 5xx it waits, then checks the branch. If GitHub already wrote the commit, it uses that commit and does not resend, because a resend would fail onexpectedHeadOid.rk_live_key, so the agent refusedsk_test_…and created no Stripe source. The fixture now has a restricted-key shape.posthog-integrationhas noaskAnswers, so the Stripe questions fell to the sentinel. The leg now passes the warehouse program's rules throughE2E_ANSWERS_FILE. "report written" is skipped when the program declares no report file.api-commits.test.ts. It was never run in CI before.Left out on purpose. These are real regressions or need a decision:
multi-source-nextexpects Postgres and Supabase as two sources, and wizard [CI] (48ac55f) nuxt/movies-nuxt-4 #1300 folds them into one.zero-sourcegets no abort. The driver goes past the no-sources screen.audit/*,flutter/localsend,migrate/triplex,self-driving/turbo-monorepo) can never open a PR, because a gitlink can't be committed.migratealso needs--product, andself-drivingrefuses CI mode.external_data_source:read, feature-flag read). That is a secrets change.Test results
pnpm test:api-commits: 6/6 pass. The landed-commit test fails with the branch check removed.pnpm test:warehouse-checks98/98,pnpm test:mcp-stub47/47,tsc --noEmitclean.109317185146and109317185224, and next-stripe now gets its own109317184957.Sources
🤖 Generated with Claude Code