Repository navigation
chore(console): bump objectui pin f995a452 → a4cff5b (17 commits / 7 releasing changesets) — required before cutting rc.4 #6159
Description
Activity
Missed the rc.4 train — retarget rc.5; urgency unchanged.
17.0.0-rc.4 was published 2026-08-07T04:17:39Z from
a10cbc77with.objectui-shastill atf995a452— via a lane that bypassed #4935 and therefore its requiredcheck:objectui-pin-fresh(details: #6169 instance, root cause issue filed alongside it). The 7 releasing changesets listed above are absent from rc.4's release record.Consequences for this chore:
- Target is now rc.5: the bump's
@objectstack/consolechangeset rides the next Version Packages cycle (chore: version packages (rc) #4935 regenerates as the rc.5 PR once release: 17.0.0-rc.4 published from a10cbc77 but the version commit never landed on main — 2026-08-03 shape repeated; merge it back before ANY further release action #6169's merge-back lands). - Still urgent, not less: the next release PR's freshness gate stays red until this lands, and the missed window only grows — re-read objectui
origin/mainat claim time (wasa4cff5bat filing; re-verify, the range may have grown). - Ordering vs release: 17.0.0-rc.4 published from a10cbc77 but the version commit never landed on main — 2026-08-03 shape repeated; merge it back before ANY further release action #6169: independent (this adds a new
.changeset/*.md; the merge-back touches none of the same files). Land in any order.
Generated by Claude Code
- Target is now rc.5: the bump's
Range refresh (2026-08-07 ~06:25Z, per the #6162 refresh duty — one open chore, updated in place):
objectui
mainhas advanceda4cff5b→ce12564. The pin now lags 27 commits / 9 releasing changesets (was 17 / 7 at filing). Newly in range, both declaredpatch:- objectui#3518 — form: bind
previousfor field rules; stop resubmitting read-only fields - objectui#3548 — plugin-grid/core: bulk buttons honor
requiredPermissions+ booleanvisible; relation fields bind by FK in predicates
Still all-
patch, no breaking annotations spotted (#6099 re-check still owed at execution time). Target remains rc.5; re-read the objectui head at claim time — the window keeps growing while this sits.
Generated by Claude Code
- objectui#3518 — form: bind
Claim: PM session (maintainer direction in chat, 2026-08-07: 「6159 你也认领,并更新到最新版本的 objectui」)
Session:session_01BickTBKm2JYSNnrtPT8ysa
Branch:claude/issue-6159-objectui-pin-bump
Worktree:objectstack-issue-6159
Domain: console pin face (.objectui-sha+ generated changeset) — maintainer-directed dispatch from chat
File surface:.objectui-sha+ one new.changeset/*.md(generated byscripts/bump-objectui.sh); ⛔ nothing else, ⛔packages/console/distis untracked and untouched
Container judgment: S/M (script writes two files; heavy build happens in CI's Console Pin Gate) →mode:subagent, shared container
Serial constraints cleared: no open PR or claim touches.objectui-sha(last bump #6097 merged this morning); in-flight #6170 dev isrelease.yml-only and #6169 (pending) is package.json/CHANGELOG/pre.json — all file-disjoint. Target: current objectuiorigin/mainhead at execution time per the maintainer's instruction (wasce12564at the 06:25Z range refresh; re-read at execution). Rides rc.5.
Generated by Claude Code
队列管家 pin-watch 机械产出:区间刷新(单张封顶 ⇒ 追评,⛔ 未开第二张)
按 2026-08-07 拍板的新条款(#6162,SKILL「入队与落地 B」),管家每轮 pin 观测附带机械产出;触发 A(objectui → objectstack,发版前侧)本轮成立:
判据 读数(2026-08-07 07:0xZ 实测) .objectui-shaf995a452(未变)objectui main7dfbeb70关系 REST compare:status=ahead/ahead_by=28/behind_by=0窗口收口判据(objectui 合并队列已空) ✅ 0 条队列分支(该仓未启用合并队列,恒空 ⇒ 判据恒满足) ⇒ 本单标题的区间已过时:立单时写的是
f995a452 → a4cff5b(17 commits / 7 releasing changesets),此后 objectui 又落地多批(03:12Z 九条、03:33Z 一条、04:07Z 六条、05:09Z 两条、06:07/06:12Z 两条依赖 bump、06:56Zchore: release packages#3248)。当前目标应为7dfbeb70,区间 28 commits;releasing changesets 数请以bump-objectui.sha口径现场重算,本座位不代算。⚠️ 与 rc.4 事故的交叉(objectstack#6169):rc.4 的发布树里.objectui-sha就是陈旧的f995a452,本单那 7 条 releasing changesets 未进 rc.4 记录;#6169 的补救落地后changeset-release/main会重算,本单因此转向 rc.5(#6169 正文已注明二者无冲突、顺序独立)。⛔ 本座位只立单/刷新读数,不执行 bump(授权面一字未变),亦不执行或触发任何发布动作(#6170)。
Generated by Claude Code
Review: ACCEPT → PR #6173, flipped ready and queued.
- Diff = declared surface exactly:
.objectui-sha(f995a452 →7dfbeb7) + the generated.changeset/console-7dfbeb704e1e.md(@objectstack/consolepatch). Nothing else;packages/console/distuntouched (untracked by design). - Range: 28 commits / 9 releasing changesets, target taken at execution time per the maintainer's direction (objectui main had advanced again; the dev passed the sha explicitly instead of trusting the sibling checkout). Notably the target is objectui's own release commit (
chore: release packages, deleting its 88 pending changesets) — the first bump to cross an objectui release; the digest's--diff-filter=Awalk + adding-commit fallback handled it, all 9 entries resolved and hand-verified. - objectui pin bump 生成的 console changeset 对破坏性变更零标注 —— digest 只认
major声明级别,而 objectui 在 v17 窗口内把破坏性声明为minor+ 正文标注 #6099 re-verification cleared properly: all 9 changeset bodies read in full + mechanical scan — every declarationpatch, zero breaking annotations. The digest is not under-labelling this range. - Two corrections to this issue's own record, both evidenced: (1) my 06:26Z refresh misattributed a releasing changeset to objectui#3518 — that commit added NO changeset (objectui#3548 contributed two, which is why the count of 9 still held); (2) the range is 28/9, not 27/9. Good falsification — and the chore(spec): flip webhook liveness ledger dead→live + webhook-materialization proof (#3490) #3518 gap itself is now filed as objectui 没有「发布性改动必须声明 changeset」闸门 —— changeset-guard.yml 的触发器决定了它只看得见已经带 changeset 的 PR(objectui#3518 因此整个从发布记录里消失) #6174 (objectui has no "releasing change must declare a changeset" gate; same release-record-loss class as Release process: prevent frontend (objectui) changesets being missed when the console pin lags #3340 through a different door). Second finding finding(bump-objectui): pin 范围跨过 objectui 的 release commit 时,digest 会先刷一屏
fatal:再报成功 —— 一个完整的结果长得像一次失败 #6175 (bump script prints scary-but-harmlessfatal:lines when the range crosses an objectui release) also verified filed. - CI fully converged green — independently verified: ESLint success 07:10:32Z, TypeScript Type Check success 07:12:45Z, Check Changeset genuinely green (this PR carries a releasing changeset —
skip-changesetcorrectly NOT applied), and Console Pin Gate success 07:15:11Z, the heavy proof that objectui at the new pin clones and builds. - Rides rc.5; repairs the release-record gap rc.4 shipped with (the 7-then-9 objectui changesets that missed rc.4's record).
Generated by Claude Code
- Diff = declared surface exactly:
- added a commit that references this issue
on Aug 8, 2026
Part of the rc.4 release train. Follow-up to the objectui lane's landed window (latest: objectui#3541).
Why now
The objectui merge queue is empty as of filing (2026-08-07 ~04:00Z) and its
mainhead isa4cff5b— the lane's rc.4 window has fully landed. Meanwhile.objectui-shaonorigin/mainisf995a452d2ca97fcc4b92ec6d004ee5571f3d6b7(last bumped this morning via #6097), which now lags 17 commits / 7 releasing changesets.This blocks the rc.4 cut:
check:objectui-pin-freshruns enforcing on the Version Packages release PR (#4935) per.github/workflows/objectui-pin-freshness.yml— a stale pin turns the release lane red. That gate exists because v16 was cut with a lagging pin and silently lost 4 frontend changes from the release record (#3340).What rides this bump (all declared
patch; verified at filing)predicate-eval-failures-warn-once(objectui#3541) — frontend half of target:v17 board item Conditional-visibility predicates (visibleWhen/visibleOn) fail OPEN and silently — a broken predicate is indistinguishable from no predicate #5149: visibility-predicate evaluation failures now warn once with source text + reason instead of failing silentlycontext-selector-per-selector-scope-key(objectui#3531) — second declared context selector no longer mirrors the first (objectui#3500)safe-translation-fallback-replace-all(objectui#3510) — fallback interpolation replaces all placeholder occurrencescreate-target-org-translated-3517,collaboration-reaction-picker-accessible-name-3478— i18n / a11y fixesreact-predicate-input-reexports-core(objectui#3511),record-form-page-dead-i18n-defaultvalue-3469— refactors, behaviour-identicalHow
Run
scripts/bump-objectui.shfrom a dedicated objectstack worktree with a sibling objectui checkout at the current objectuiorigin/mainhead (re-read at claim time;a4cff5bas of filing). Precedent: #6097. Do not hand-editpackages/console/dist(not tracked; built bybuild-console.sh).Caveats
major声明级别,而 objectui 在 v17 窗口内把破坏性声明为minor+ 正文标注 #6099 (open): the bump digest only flagsmajor-declared breaking changes, while objectui declares v17-window breaking asminor+ body annotation. Checked at filing: all 7 changesets in this range declarepatchand none carries a breaking annotation — re-verify if the range has grown by execution time.@objectstack/consolechangeset). No file overlap with queued chore(release): 发版状态对账 —— main 版本对齐 2026-08-03 已发布的 17.0.0-rc.3 #6149 (it touches onlypackage.jsonversion fields; this bump touches.objectui-sha+ a new.changeset/*.md).