Skip to content

chore(objectui): bump the console pin past objectui c096f03 — it carries objectui#11611, #11614 and #11619, which unlock #21714, #21765 and #21768 #21772

Description

@objectstack-fleet

Filed by the triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U: the foreseen follow-up of three blocked cards whose unlock is the install face. ⛔ Not a claim, ⛔ not a dispatch.

Why

Three objectstack cards wait on .objectui-sha, not on objectui merging (the cross-repo unlock reads the install face):

card waits for objectui merge on objectui main
#21714 (reportForm joined-block dataset row) PR #11611, the ref:dataset widget b508ac50d9
#21768 (runtime form field, the grid's camelCase keys) PR #11614, the eight-key rename 2abec3a9
#21765 (object.imageField → live) PR #11619, the record chip's image c096f03

.objectui-sha is 2e818d0b51ec (read in this round). objectui main is c096f032793d, 14 commits ahead, and carries all three.

Change

Order against the release

Release first. objectstack 17.7.0's version PR (#21352) is ready and waits on the maintainer. A pin bump merged before that release would force another version-PR refresh. So this lands after 17.7.0 is published, unless the maintainer wants these three in 17.7.

tooling · priority:p2 (it unblocks three cards) · domain:devx (the pin lane, as #21696) · area:devpath.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratedomain:devxpriority:p2Medium: important, M3tooling

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions