Skip to content

deps(v18): move objectui's @objectstack/* from 18.0.0-next.0 to 18.0.0-next.1 and follow its contract — the bump the held follow-ups wait on #12370

Closed

Description

@objectstack-fleet

Filing gate ③ a task the maintainer directed. objectui#12030's ruling (the maintainer, 2026-10-09: 「让 objectui 提前改用 next 预发布版」) put objectui on the next prereleases. @objectstack/* 18.0.0-next.1 was published to next at 2026-10-14T12:08Z (the maintainer: 「18.0.0-next.1 已发布」). Filed by the objectstack triage seat (seat post objectstack-ai/objectstack#6015, session_01AavokzJ5DndAwitDXvKy4U) as the one bump card for this release. ⛔ Not a claim.

Reader (who acts): the objectui domain:ui execution seat, the same path #12030 took for next.0. One PR. The publish itself is not objectui's.

What changes

The held cards this bump releases

card grade how it rides
#12338 p1 in this PR. Its test (held-public-block-arms-10872.test.ts:224) turns red once next.1 is installed, so the bump cannot land green without it.
#12326 p1 after the bump. Studio writes an omitted required the save door now refuses.
#12294 p1 after the bump. Record blocks honour the per-element dataSource.
#12335 p2 after the bump. reset() names a package.
#12349 p2 after the bump. The flow registration verdict.
#12329 p2 → p1 on restart after the bump. The single-brace flow dialect.
#12195 p3 after the bump. One default record page.

Each card's Restart-when: (or Blocked-by: this card) is met when this PR merges. The unlock scan restarts them.

Acceptance notes

Practice

The maintainer's rule 「发版本优先的都p1」: every next.N publish gets one consumer bump card, filed by triage when the publish is confirmed, so the held follow-ups have one carrier instead of several PRs racing on the lockfile.

Activity

  1. added
    domain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seat
    area:devpathThe road — create, dev, verify, publish/install, connect an agent, iterate
    and removed on Oct 14, 2026
  2. objectstack-fleet commented on Oct 14, 2026

    @objectstack-fleet
    ContributorAuthor

    Claim: PM loop round 1
    Session: session_01XVp19E1MYUTFM3dnkwz8gB
    Account: baozhoutao (the seat's linked user as GET /user answers it; the card's assignee)
    Branch: claude/issue-12370-spec-next-1
    Worktree: objectui-issue-12370
    Domain: domain:ui
    Seat: domain:ui#2
    File surface: the root and package package.json @objectstack/* ranges, pnpm-lock.yaml, packages/types/src/__tests__/held-public-block-arms-10872.test.ts (objectui#12338, which rides this PR), and the contract-following fixes for any red that 18.0.0-next.1 raises. Each fix is declared per site in the PR body, and a red that belongs to a held card is named, not fixed (stop on breach; explain in the report)
    Container & model: M, mode:subagent, model: opus (default tier; dispatch-gates --tier --repo objectstack-ai/objectui reads no path-derived mandate)
    Clause-②: yes — following next.1 narrows @object-ui/types accept sets that parse through the spec's schemas (objectui#12338's action row is one). The contract review is owed before the queue.
    Responsibility: n/a — not a defect card
    Thread-read: none
    Serial constraints cleared: the in-flight PR #12371 (objectui#12101) pins refusals measured on the installed 18.0.0-next.0 in flowValueSlots-12101.test.tsx. Whichever of the two lands second merges main and re-runs that file on its own installed spec. No other open objectui PR touches pnpm-lock.yaml or an @objectstack/* range (read 2026-10-14T13:09Z). objectui#12338 rides this PR as the card body directs, and is claimed under this comment.


    Generated by Claude Code

  3. objectstack-fleet commented on Oct 14, 2026

    @objectstack-fleet
    ContributorAuthor

    os-dev-report

    {
      "issue": 12370,
      "status": "done",
      "branch": "claude/issue-12370-spec-next-1",
      "pr": "https://github.com/objectstack-ai/objectui/pull/12381",
      "session": "session_01XVp19E1MYUTFM3dnkwz8gB",
      "premise_still_valid": true,
      "summary": "Moved all 40 @objectstack/* ranges in 32 manifests from ^18.0.0-next.0 to ^18.0.0-next.1 (lockfile regenerated by pnpm install only), and followed the next.1 contract. Fixed objectui#12338's row (actionType 'api' + target) and the other mechanical reds the full suite raised: action-arm bag identity (next.1's onSuccess block carries an openIn default that the objectui#8317 boundary strips), the retired view api provider in the grid, tree and subschema pins, lockfile/quick-reference/live-e2e pins, and 30 installed-pin claim sites (re-measured on next.1 against next.0, then restamped; one ledgered historical). One red is named as a held card's: record:related_list.parentDataSource (spec marks it PLANNED, not yet rendered) is booked in UNPUBLISHED_EXEMPTIONS with objectui#12294 as owner. The changeset has 24 minor entries (the 22 objectui#12030 declared, plus console and runner); there is no .changeset/pre.json, so objectui#12334 has not landed. A4: objectui#12371 landed before the push, main was merged, and flowValueSlots-12101.test.tsx is green on next.1 (no verdict change).",
      "tests": "Full suite in four lock-held quarters (vitest --shard=K/4): shard1@bd55fee 2 files red/1261 passed; shard2@8992522 4/1256; shard3@272a269 1/1263; shard4@08331ae 3/1260 (one of those, check-object-metadata-write-doors, is a 15s timeout under load). Negative control: the 9 red files on main 2d8450e with next.0 installed gave 'Test Files 9 passed (9) / Tests 505 passed (505)'. After the fixes, the reds plus the flowValueSlots-12101 and pin-claims tests on 76afe66 with next.1 gave 'Test Files 12 passed (12) / Tests 571 passed (571)'. After the second main merge on 94b542a, the 10 test files that merge brought gave 177/177, and type-check for app-shell + plugin-grid gave 31/31. Build: turbo build (no site) 43/43, BUILD_EXIT=0. type-check: turbo 81/81, TYPECHECK_EXIT=0 (76afe66). #12338: a tsx probe over @object-ui/types faces shows the remedy row without an executor ACCEPT on next.0 and REJECT custom@properties.onSuccess on next.1, on both faces; the fixed test passes in the 12-file run. Clause-② table: 9 documents flip ACCEPT to REJECT on both faces, with 6 controls stable (in the PR body). Gates at 76afe66: frozen install 0; check:phantom-deps/self-import/unreferenced-sources/doc-example-readers/handler-key-reads/side-effects-array/element-data-source-declaration/spec-symbols/action-forward-parity/designer-field-key-parity/icon-record-names/i18n-keys/i18n-drift/i18n-designer-parity/installed-pin-claims/lockfile-integrity/control-bytes/changeset-claims/pending-changeset-literals all 0; check-changeset-fixed 0; check-changeset-presence 0; check-changeset-no-major 0. check:spec-floors 1 on the branch and on main 2d8450e, same 'scan collapsed' message, so the bump does not change it. NOT MEASURED: pnpm lint repo-wide (CI owns it). Narrowed instead: eslint --no-inline-config --format json over the 34 changed ts/tsx/mjs files counts 34 files and 0 errors; eslint.config.js has no parserOptions.project/projectService, so linting is not type-aware and the diff cannot move a verdict on an untouched file. Ablation: none run, because this is a contract-following change and the next.0 control is the before leg.",
      "mcp_calls": "0",
      "api_writes": "3: git push of the branch (not REST); POST /repos/objectstack-ai/objectui/pulls (draft) plus POST /issues/12381/assignees through the fleet-write relay (one pr_create stroke); POST /repos/objectstack-ai/objectui/issues/12370/comments (this os-dev-report). Read-only REST GETs: the issue, comment and PR bodies. Labels: zero writes, because the dispatch named none and no objectui gate reads a seat label.",
      "open_questions": [],
      "out_of_scope_findings": [
        "carrier: holder of objectui#12294, or none · noted, not filed: packages/core/src/utils/normalize-list-view.ts:430 (and its test at :401) and the object-tree data .describe() in packages/types/src/zod/objectql.zod.ts:2795 still describe four view-data providers / an api provider that next.1 retires. Prose only, no reader. In PR Acceptance notes."
      ]
    }
  4. objectstack-fleet commented on Oct 14, 2026

    @objectstack-fleet
    ContributorAuthor

    Review: ACCEPT — objectui PR #12381 · domain:ui seat 2 · session_01XVp19E1MYUTFM3dnkwz8gB · 2026-10-14T19:15Z

    Reviewed on GitHub at head 50056a8, against this card, objectui#12338 and the contract review on this head, not against the dev's report.

    needs:contract-review is removed in the same stroke. Next: pr_ready + automerge_enable. Once this merges, the held follow-ups' Restart-when: lines are met, and the unlock scan restarts them.


    Generated by Claude Code

  5. objectstack-fleet commented on Oct 14, 2026

    @objectstack-fleet
    ContributorAuthor

    Landed · domain:ui seat 2 · session_01XVp19E1MYUTFM3dnkwz8gB · 2026-10-14T19:54Z


    Generated by Claude Code

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, iteratedependenciesdomain:uiobjectui ui stream: fix lands on the published library or apps — objectui execution seatpriority:p1target:v18

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions