[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

The changelog information of each package has been omitted from this message, as the content exceeds the size limit.

@objectstack/hono@18.1.0

@objectstack/cli@18.1.0

@objectstack/cloud-connection@18.1.0

@objectstack/console@18.1.0

@objectstack/core@18.1.0

@objectstack/driver-memory@18.1.0

@objectstack/driver-sql@18.1.0

@objectstack/driver-turso@18.1.0

@objectstack/formula@18.1.0

@objectstack/lint@18.1.0

@objectstack/metadata-core@18.1.0

@objectstack/metadata-protocol@18.1.0

@objectstack/objectql@18.1.0

@objectstack/platform-objects@18.1.0

@objectstack/plugin-approvals@18.1.0

@objectstack/plugin-audit@18.1.0

@objectstack/plugin-auth@18.1.0

@objectstack/plugin-hono-server@18.1.0

@objectstack/plugin-security@18.1.0

@objectstack/plugin-sharing@18.1.0

@objectstack/rest@18.1.0

@objectstack/runtime@18.1.0

@objectstack/service-datasource@18.1.0

@objectstack/service-messaging@18.1.0

@objectstack/service-settings@18.1.0

@objectstack/spec@18.1.0

@objectstack/account@18.1.0

@objectstack/setup@18.1.0

@objectstack/studio@18.1.0

@objectstack/client@18.1.0

@objectstack/client-react@18.1.0

@objectstack/connector-mcp@18.1.0

@objectstack/connector-openapi@18.1.0

@objectstack/connector-rest@18.1.0

@objectstack/connector-slack@18.1.0

create-objectstack@18.1.0

@objectstack/driver-mongodb@18.1.0

@objectstack/driver-sqlite-wasm@18.1.0

@objectstack/mcp@18.1.0

@objectstack/metadata@18.1.0

@objectstack/metadata-fs@18.1.0

@objectstack/observability@18.1.0

@objectstack/embedder-openai@18.1.0

@objectstack/knowledge-memory@18.1.0

@objectstack/knowledge-ragflow@18.1.0

@objectstack/organizations@18.1.0

@objectstack/plugin-dev@18.1.0

@objectstack/plugin-email@18.1.0

@objectstack/plugin-pinyin-search@18.1.0

@objectstack/plugin-webhooks@18.1.0

@objectstack/service-analytics@18.1.0

@objectstack/service-automation@18.1.0

@objectstack/service-cache@18.1.0

@objectstack/service-cluster@18.1.0

@objectstack/service-cluster-redis@18.1.0

@objectstack/service-i18n@18.1.0

@objectstack/service-job@18.1.0

@objectstack/service-knowledge@18.1.0

@objectstack/service-mailbox@18.1.0

@objectstack/service-package@18.1.0

@objectstack/service-print@18.1.0

@objectstack/service-queue@18.1.0

@objectstack/service-realtime@18.1.0

@objectstack/service-sms@18.1.0

@objectstack/service-storage@18.1.0

@objectstack/skills@18.1.0

@objectstack/trigger-api@18.1.0

@objectstack/trigger-record-change@18.1.0

@objectstack/trigger-schedule@18.1.0

@objectstack/types@18.1.0

@objectstack/verify@18.1.0

@objectstack/connector-imap@18.1.0

@objectstack/sdui-parser@18.1.0

@objectstack/example-crm@4.0.101

@objectstack/example-multi-package@0.0.8

@objectstack/example-showcase@0.3.23

@objectstack/example-todo@4.0.101

@objectstack/example-embed-objectql@0.0.41

@objectstack/dogfood@0.0.49

@objectstack/downstream-contract@0.0.47

@objectstack/http-conformance@0.1.9

[objectstack-fleet]

GA cut-precondition reading for 18.1.0 · domain:devx seat 1 (seat post #6023) · os-elon-musk · session_01LKHDniRQSWjRJyDtacwpEd · 2026-10-23T00:47Z. ⛔ Not a release act: the seat does not refresh, approve, merge or publish. It also changes no labels. The maintainer asked for this reading. It covers the two GA-only items in docs/releases-maintenance.md (:330, :446–450): the #7275-A cut precondition and the board-clearing pass.

Verdict: not clear. Two precondition items fail and one board is unreadable. #24876 itself is current against main, but none of its CI has run yet.

The rule being read

• No producer files the final console bump card at the release-cut moment — the #6162 chore is keyed to a settled window, and the card it does file never reaches the release board #7275, maintainer ruling 5237208028 (2026-08-10), verbatim: "Before a cut, the release protocol takes the pin readout once; if the pin lags, the console bump card must exist and be boarded (target:v17) or explicitly waived with the standard accepted-for-GA comment."
• Standing text, .claude/skills/pm-dispatch/references/seat-post-protocol.md 「发版板运维」 on origin/main 9dc1f42d50:
  • :89 「发版前置:清板动手之前先取一次 pin 读数,⛔ 一次即止不是重扫。」
  • :90 「pin 滞后 ⇒ console bump 单必须已存在且已上板,或按标准形态明示接受。」
  • :91 「两者都不成立 ⇒ ⛔ 不 cut。」
  • :83 「归零 = 可发版指三张板都空,单看主仓归零不是。」
  • :86–87: each board item takes one of three dispositions: fix it, take it off the board, or accept it explicitly. Explicit acceptance means removing the label, posting an accepted-for-GA comment, and listing the item under known issues in the release notes.
• The major for 18.1.0 is 18, so the board label is target:v18.

1. Pin readout (#7275-A), taken once

reading	command	result	read at
committed pin	git show origin/main:.objectui-sha (main 9dc1f42d50)	0d12e95361b2, moved by #25262 (cc8d886d40)	2026-10-23T00:43Z
objectui main	git ls-remote https://github.com/objectstack-ai/objectui refs/heads/main	5fef032b1ada	2026-10-23T00:46Z
lag	git rev-list --count 0d12e95361b2..origin/main in objectui; merge-base --is-ancestor holds	2 commits behind	2026-10-23T00:43Z
what the lag carries	git diff --name-only 0d12e95361b2 origin/main -- .changeset/	b911ebb objectui#13323 (#13328): .changeset/13323-one-read-per-open.md, @object-ui/react minor + @object-ui/app-shell patch (a nav entry and a page element bound to the same API read make one request per open). 5fef032 objectui#13327 (#13329): CI only, empty changeset	2026-10-23T00:43Z
console bump card or PR	every open issue and PR in objectstack (124), matched on pin|bump|objectui-sha and on objectui|console; open PRs (16) read by title and branch	none	2026-10-23T00:44Z
explicit waiver	accepted-for-GA comments on this PR and on the board cards	none	2026-10-23T00:46Z

Reading: the pin lags. No bump card exists, and the lag has no waiver ⇒ :91, ⛔ no cut until one of the two holds. This is not a currency gate (#10134 removed those, and a lagging pin is not a defect in itself). The rule asks only that the shipped console revision be a recorded decision, either a boarded bump or a waiver.

2. Board-clearing pass (label:target:v18 is:open, three boards)

board	query	result	read at
objectstack	GET repos/objectstack-ai/objectstack/issues?labels=target:v18&state=open	2: #15194 ([epic] ADR-0131, tracking, pm:epic) and #15212 (C8 parent, pm:blocked)	2026-10-23T00:41Z
objectui	GET repos/objectstack-ai/objectui/issues?labels=target:v18&state=open	0	2026-10-23T00:41Z
cloud	GET repos/objectstack-ai/cloud/issues?labels=target:v18&state=open	not readable by this seat (HTTP 403)	2026-10-23T00:41Z

• Neither objectstack item has a disposition. Each has had target:v18 since 2026-09-04 (label events: hotlong, 2026-09-04T05:44Z and 2026-09-04T06:06Z). Both were still on the board when 18.0.0 shipped. Neither carries an accepted-for-GA comment.
• What they hold now. The epic seat's reconciliation on feat(spec,drivers,objectql,plugin-security): organization_id NOT NULL per cleared table; one predicate for Layer 0 and every driver; both orWhereNull arms, the __global__ sentinel and the #13491 ledger retire (ADR-0131 D1/D8/D9) — protocol 18 #15212 (6339761793, 2026-10-22T11:35Z) says every planned step of the 18.x line is closed. The remaining scope is child cards refactor(objectql)!: retire the PLATFORM_OBJECT_TENANCY ledger (ADR-0131 D13) — the bypassTenantAudit mute becomes structural, and the [tenant-audit] warning stops telling a wall-exempt write to pass a tenantId #25201, fix(service-settings): the tenant and user rungs stop reading organization-less sys_setting rows as every organization's fallback (ADR-0131 D8) — measure first #25202, fix(core,plugin-security): ADR-0131 8c-2 review carriers — guard a sys_organization insert that moves the platform-admin anchor, pin the ceremony's NULL admin_full_access attribution, one Default Organization definition #25208, chore: ADR-0131 small carriers — resolveDeclaredRuleScopes checks the raw page length, the semantic-entry and ceremony wording, and the help texts and docblocks that still say NULL organization means global #25203 and fix(organizations)!: retire claimOrphanOrgRows — it gives organization-less rows to the first organization, an owner by guess that ADR-0131 D9 and D10 forbid (measured 6342754850) #25204, and none of them is on the board. The line rules (6266750393, 6270035914 on [epic] ADR-0131 — total organization ownership: no NULL organization_id (v18 line) #15194) keep main releasable after every merge.
• Not on any board, for completeness:
  • hotcrm is not one of the protocol's three boards and has no target:* label.
  • objectstack also carries a stray target:18 label (no v) with 0 open items.
• Reading: the board is not cleared. The objectstack board has 2 items without a disposition, and the cloud board could not be read. The maintainer chooses each disposition. Under :86, an item the cut does not wait for is either taken off the board or accepted explicitly. It does not stay on the board in silence.

3. Is #24876 current, and has its CI run?

reading	command	result	read at
main tip	git ls-remote origin refs/heads/main	9dc1f42d50 (#25307, committed 2026-10-22T23:55Z)	2026-10-23T00:46Z
head	git ls-remote origin refs/heads/changeset-release/main	a93805a2e1, parent 9dc1f42d50, rendered by the scheduled Release run 39877864123 (2026-10-23T00:23Z, success)	2026-10-23T00:46Z
behind main	git rev-list --count $(git merge-base origin/main a93805a2e1)..origin/main	0	2026-10-23T00:44Z
changesets consumed	.changeset/*.md count on main and on head	191 → 0. @objectstack/spec 18.0.0 → 18.1.0. Head pin = main pin	2026-10-23T00:44Z
check-runs on head	GET .../commits/a93805a2e1/check-runs	total 0. Commit status: publish-smoke / packed-tarballs success (1/1)	2026-10-23T00:44Z
workflow runs on head	GET .../actions/runs?head_sha=a93805a2e1	15 pull_request runs, all action_required (CI, Lint & Type Check, Scaffold E2E, Spec Liveness, …). mergeable_state: blocked	2026-10-23T00:44Z
main CI on 9dc1f42d50	same query, head_sha 9dc1f42d50	merge_group CI, Lint, Spec Liveness and Governed Surface: success. push CI: in progress	2026-10-23T00:45Z

Reading: the version PR is current and no refresh is needed now. If anything lands on main before the merge, including a pin bump from §1, the PR goes stale. A merge of a stale PR ships that code while its changesets stay pending, which is the #21361 class. No check has run on this head. On #24524 the PR checks ran as attempt 2, started by os-zhuang at 2026-10-20T11:10Z. This head needs the same approval.

What the maintainer does next (every step is the maintainer's; the seat takes no release act)

1. Pin (No producer files the final console bump card at the release-cut moment — the #6162 chore is keyed to a settled window, and the card it does file never reaches the release board #7275-A). Pick one:
   • (a) Waive. Post an explicit accepted-for-GA comment that names 0d12e95361b2 as 18.1.0's console. That means 18.1.0 ships without objectui#13323, and fix(objectql): pick the find failure log level from the cause — "the table is not provisioned yet" is not "the read failed" (#13273) #13327 is CI-only.
   • (b) Bump. Have a console bump card filed and boarded target:v18. The triage seat boards it, as the single producer for this backlog. Land the bump PR (scripts/bump-objectui.sh) before the cut, then go to step 4.
2. Board. For [epic] ADR-0131 — total organization ownership: no NULL organization_id (v18 line) #15194 and feat(spec,drivers,objectql,plugin-security): organization_id NOT NULL per cleared table; one predicate for Layer 0 and every driver; both orWhereNull arms, the __global__ sentinel and the #13491 ledger retire (ADR-0131 D1/D8/D9) — protocol 18 #15212, choose one of: fix, take off the board, or accept explicitly. Accepting means removing the label, posting an accepted-for-GA comment, and listing the item under known issues.
3. Cloud board. Read label:target:v18 is:open on objectstack-ai/cloud, or have the cloud seat read it. Then dispose of each item as in step 2.
4. Refresh if main moved. If main has moved past 9dc1f42d50, run Actions → Release → Run workflow with refresh_version_pr checked. That is the bookkeeping lane only, with no publish. Wait for the refreshed PR.
5. CI. Approve the pending workflow runs on this PR and wait for green.
6. Changelog. Review the generated changelogs on this PR.
7. Merge and approve. Merge this PR. Then approve the release environment deployment, Publish 18.1.0 to npm (awaiting approval).
8. Re-read before merging. This reading is a snapshot. If time passes before the merge, re-read §1 and §3 first.

Not measured: the cloud board (no read access from this seat).