Repository navigation
fix(build): regenerate stale ui index after concurrent merges - #18799
chenmingwei23 wants to merge 1 commit into
Conversation
|
Unblocks main build; please merge first. |
UX Review (Opus 5.5, fork) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5, fork) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Before merging, re-run What this change shipsInventory (2 items) — 2 justifiedIntent: get
[FIRST-PRINCIPLES-REVIEWED] f695dfe Description read[DESCRIPTION-READ] fe5fd910639cd1fd81649ef586e8bf1cd478e04b46feb4f2da293109e0cdbe11 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5, fork) — ✅ PASSDesign-level review of Design-Verdict: PASS Before merging, re-run [DESIGN-REVIEWED] f695dfe Description read[DESCRIPTION-READ] f3812246f6bcf7204999df6c0b9730dccbc2360a953d8917f8898fda9690691a That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review (fork) — ✅ no blocking findingsReviewed |
GPT 6.1 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
|
Superseded: main's index is fresh again after #18782. |
Why this change
mainis red on every platform (Build Wheel"Build frontend",Build Desktop, E2E).npm run buildinwebsite/fails at its first step,gen-ui-index.mjs --check:The committed UI index is stale against its own sources. Several PRs changed the index's inputs (dashboard components and the settings registry) without regenerating the committed
src/kiro_crew/docs/ui-index.generated.json. The index was last regenerated at #18443 (last green build); builds have been red since the next merge. The most recent missing input is thenotifications.sound-category-dictationsetting added in #17923, which merged within ~5 seconds of #17732, so each PR was green alone but the committed index was left out of sync once they landed together.This is a CI-only, generated-artifact fix. It does not change any product behaviour, UI, or copy for users, and it does not change the index generator or its inputs.
What changed
Ran
npm run gen:uiinwebsite/on the currentmaintip and committed the result. The only change is tosrc/kiro_crew/docs/ui-index.generated.json:setting:notifications.sound-category-dictationentry and its label strings in all 12 locales, andinput_digestand the generated/setting coverage counts to match.gen:uireported no change towebsite/src/uiLocations/guidePlans.gen.ts, so the diff is the index file only.Verification
On this branch, in
website/:node scripts/gen-ui-index.mjs --check ...exits 0 ("up to date"); it failed with the stale-digest error onmainbefore the regeneration.npm run buildcompletes (gen:ui check, tsc, and vite build all pass).Backwards compatibility
Compatible: a generated artifact is brought back in sync with its inputs. No code or schema changes; nothing removed.