Repository navigation
main is red: QUICK_REFERENCE.md "Current Release" still says 17.4.0 after the 17.5.0 release commit — shard-3 gate fails on main and every open PR #4642
Description
Activity
Claim: PM loop round 1 (main-red stop-bleed)
Session:session_01RnQd8iMMUwXQEV1crFmQiQ
Branch:claude/issue-4642-quick-reference-1750
Worktree:objectui-issue-4642
Domain:repo:objectui
File surface:QUICK_REFERENCE.md(the "Current Release" block only) (stop on breach; explain in the report)
Container & model: S mechanical,mode:subagent,model: sonnet
Serial constraints cleared: no in-flight card or open dev PR touchesQUICK_REFERENCE.md(#4637 scripts/examples; #4638/#4641 app-shell; #4639 manifests+lockfile — the manifests it bumps are dependency ranges, not the workspaceversionfields this doc derives from; checked this round).
Generated by Claude Code
{ "issue": 4642, "status": "done", "branch": "claude/issue-4642-quick-reference-1750", "pr": "https://github.com/objectstack-ai/objectui/pull/4643", "premise_still_valid": true, "summary": "QUICK_REFERENCE.md's \"Current Release\" block had exactly one stale row: Version read 17.4.0 while every @object-ui/* manifest carries 17.5.0 since the release commit 5bf5d2cb6. Bumped that single row to 17.5.0; every other anchored row (Spec, Client, Node.js, pnpm, React, TypeScript) already matched its manifest anchor and needed no change. Scope was held to QUICK_REFERENCE.md only, one-line diff.", "tests": "At HEAD 275c7701b: `pnpm exec vitest run scripts/__tests__/quick-reference-current-release-4143.test.ts` -> 8/8 passed (was 2 failed / 6 passed before the fix, confirming baseline red). `node scripts/check-control-bytes.mjs QUICK_REFERENCE.md` -> OK (scanned 4174 tracked text files). `node scripts/check-changeset-presence.mjs` -> \"0 of them under the src/ of a package the release covers ... No source of a released package changed in this range, so no changeset is owed.\" No skip-changeset label exists in this repo per content/docs/guide/ci-cd-pipeline.md's Changeset Presence section (the exemption is derived by the gate, not a label) -- ran the gate's own script locally to confirm no changeset is owed instead of applying a nonexistent label.", "open_questions": [], "out_of_scope_findings": [] }
Generated by Claude Code
- added a commit that references this issue
on Aug 20, 2026 - added a commit that references this issue
on Aug 23, 2026
Filed by the
repo:objectuiseat (sessionsession_01RnQd8iMMUwXQEV1crFmQiQ, round 1, 2026-08-14). Duplicate-searched (semantic: QUICK_REFERENCE / current release / 17.4.0): zero open cover.The defect
The v17.5.0 release commit (
5bf5d2cb6, currentorigin/main) moved every@object-ui/*manifest to17.5.0but did not updateQUICK_REFERENCE.md's "Current Release" block, which still states17.4.0(line 114). The gate built for exactly this drift —scripts/__tests__/quick-reference-current-release-4143.test.ts— fails with two assertions:QUICK_REFERENCE.md must state the workspace version as "17.5.0"(line ~195);["17.4.0"]as a literal no manifest produced (line ~365).Blast radius — measured, not inferred
Test (shard 3/4) is red on the base branch itself, so every open PR inherits the failure regardless of its diff. Confirmed by identical signature on PR #4637, whose diff touches only
scripts/regenerate-catalog-index.py+examples/schema-catalog(log pulled from job 94747819897, head7db3160). PRs #4638 / #4639 / #4641 show the same shard red on the same base. Until this lands, nothing in this repo can go green.Re-check commands:
git grep -n "17\.4\.0" origin/main -- QUICK_REFERENCE.md(hit at :114 ⇒ still broken)git show origin/main:packages/core/package.json | grep '"version"'(17.5.0)pnpm exec vitest run scripts/__tests__/quick-reference-current-release-4143.test.tsScope
Update the "Current Release" block to state
17.5.0(and re-derive any other row the test flags). Nothing else — the gate did its job; this card is the doc catching up with the release. If other underived literals surface in the same block, fix them in the same pass per the test's derived-values list.