chore: version packages (next)

[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.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

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

@objectstack/hono@18.0.0-next.3

@objectstack/cli@18.0.0-next.3

@objectstack/cloud-connection@18.0.0-next.3

@objectstack/console@18.0.0-next.3

@objectstack/core@18.0.0-next.3

@objectstack/driver-sql@18.0.0-next.3

@objectstack/driver-turso@18.0.0-next.3

@objectstack/metadata-core@18.0.0-next.3

@objectstack/metadata-protocol@18.0.0-next.3

@objectstack/objectql@18.0.0-next.3

@objectstack/platform-objects@18.0.0-next.3

@objectstack/plugin-approvals@18.0.0-next.3

@objectstack/plugin-audit@18.0.0-next.3

@objectstack/plugin-auth@18.0.0-next.3

@objectstack/plugin-hono-server@18.0.0-next.3

@objectstack/plugin-security@18.0.0-next.3

@objectstack/rest@18.0.0-next.3

@objectstack/runtime@18.0.0-next.3

@objectstack/service-automation@18.0.0-next.3

@objectstack/service-package@18.0.0-next.3

@objectstack/service-print@18.0.0-next.3

@objectstack/service-storage@18.0.0-next.3

@objectstack/spec@18.0.0-next.3

@objectstack/account@18.0.0-next.3

@objectstack/setup@18.0.0-next.3

@objectstack/studio@18.0.0-next.3

@objectstack/client@18.0.0-next.3

@objectstack/client-react@18.0.0-next.3

@objectstack/connector-mcp@18.0.0-next.3

@objectstack/connector-openapi@18.0.0-next.3

@objectstack/connector-rest@18.0.0-next.3

@objectstack/connector-slack@18.0.0-next.3

create-objectstack@18.0.0-next.3

@objectstack/driver-memory@18.0.0-next.3

@objectstack/driver-mongodb@18.0.0-next.3

@objectstack/driver-sqlite-wasm@18.0.0-next.3

@objectstack/formula@18.0.0-next.3

@objectstack/lint@18.0.0-next.3

@objectstack/mcp@18.0.0-next.3

@objectstack/metadata@18.0.0-next.3

@objectstack/metadata-fs@18.0.0-next.3

@objectstack/observability@18.0.0-next.3

@objectstack/embedder-openai@18.0.0-next.3

@objectstack/knowledge-memory@18.0.0-next.3

@objectstack/knowledge-ragflow@18.0.0-next.3

@objectstack/organizations@18.0.0-next.3

@objectstack/plugin-dev@18.0.0-next.3

@objectstack/plugin-email@18.0.0-next.3

@objectstack/plugin-pinyin-search@18.0.0-next.3

@objectstack/plugin-sharing@18.0.0-next.3

@objectstack/plugin-webhooks@18.0.0-next.3

@objectstack/service-analytics@18.0.0-next.3

@objectstack/service-cache@18.0.0-next.3

@objectstack/service-cluster@18.0.0-next.3

@objectstack/service-cluster-redis@18.0.0-next.3

@objectstack/service-datasource@18.0.0-next.3

@objectstack/service-i18n@18.0.0-next.3

@objectstack/service-job@18.0.0-next.3

@objectstack/service-knowledge@18.0.0-next.3

@objectstack/service-mailbox@18.0.0-next.3

@objectstack/service-messaging@18.0.0-next.3

@objectstack/service-queue@18.0.0-next.3

@objectstack/service-realtime@18.0.0-next.3

@objectstack/service-settings@18.0.0-next.3

@objectstack/service-sms@18.0.0-next.3

@objectstack/skills@18.0.0-next.3

@objectstack/trigger-api@18.0.0-next.3

@objectstack/trigger-record-change@18.0.0-next.3

@objectstack/trigger-schedule@18.0.0-next.3

@objectstack/types@18.0.0-next.3

@objectstack/verify@18.0.0-next.3

@objectstack/connector-imap@18.0.0-next.3

@objectstack/sdui-parser@18.0.0-next.3

@objectstack/example-crm@4.0.100-next.3

@objectstack/example-multi-package@0.0.7-next.3

@objectstack/example-showcase@0.3.22-next.3

@objectstack/example-todo@4.0.100-next.3

@objectstack/example-embed-objectql@0.0.40-next.3

@objectstack/dogfood@0.0.48-next.3

@objectstack/downstream-contract@0.0.46-next.3

@objectstack/http-conformance@0.1.8-next.3

[objectstack-fleet]

⚠️ Hold before merging: this Version Packages PR is behind main by changesets · domain:devx seat 2 · session_016PVjjuVPte5XEJvaQx1E4t · 2026-10-16T06:55Z

This PR was cut from base f606ba2e25. origin/main (1ecb08a1c, read at this act) has since gained two changeset-bearing merges, #23817 and #23814. Merged as it stands, it would ship those changesets' code in the next prerelease with no CHANGELOG entry for them.

That is the defect #23818 (priority:p1, dispatched in this act) measures on 18.0.0-next.2: #23481 was cut from a base main had passed, and 11 changesets shipped unlisted, among them the BREAKING #23610 refusal.

• What this PR also carries: those 11 unconsumed changesets. They would be listed under this prerelease's heading, though their code shipped in 18.0.0-next.2. release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818 decides how they are labelled. Its PR measures two routes: a "shipped in next.2" lead line on each changeset, or an in-place entry in next.2's sections.

• What release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818 adds: a guard, so that a Version Packages PR behind main by a changeset is refused or refreshed.

• Suggested order, the release owner's call:

  1. Land release(next): 18.0.0-next.2 shipped 11 changesets with no CHANGELOG entry (the version PR merged behind main; #21361's class, in pre mode) #23818's PR.
  2. Regenerate this PR from that main, with release.yml's refresh_version_pr or its 6-hourly schedule.
  3. Then merge.

  Merging this head now repeats the defect for fix(spec): four metadata type descriptions Setup shows are plain admin sentences #23817 and feat(plugin-audit): sys_activity gains writer-stamped read-rule columns with an idempotent backfill, and the withheld-row rule is a predicate with no SYSTEM pre-scan (ADR-0139 E6) #23814.

⛔ This seat performs no release act. This note is information for whoever merges.

---

Generated by Claude Code

[objectstack-fleet]

Hold lifted: this Version Packages PR is current with main at this act · domain:devx seat 2 · session_016PVjjuVPte5XEJvaQx1E4t · 2026-10-16T08:45Z

This supersedes the seat's hold note 6209924889. The seat re-cut this PR through the relay's release.yml refresh_version_pr stroke (run 38875444505, success), after #23835 landed.

Readings at this act:

• Base. The head is dedc6fe388, cut from base 3c080a65c8, which is origin/main now. The CLI moves to 18.0.0-next.3.
• Changesets. The version commit's tree holds 0 top-level changesets. All 13 named in the hold are now under .changeset/pre/: the 11 that 18.0.0-next.2 shipped unlisted, plus feat(plugin-audit): sys_activity gains writer-stamped read-rule columns with an idempotent backfill, and the withheld-row rule is a predicate with no SYSTEM pre-scan (ADR-0139 E6) #23814's 23731-activity-changed-fields and fix(spec): four metadata type descriptions Setup shows are plain admin sentences #23817's 23808-type-descriptions-plain.
• CHANGELOGs. The 11 render with their lead line **Shipped in 18.0.0-next.2**, …: 19 lines across 12 CHANGELOG.md files.

main's queue keeps landing, at about 3 changeset-bearing merges an hour over the last day. A changeset that lands between this cut and the merge ships in next.3 without an entry. #23818's reworked #23833 handles that case at the next cut, so it is not a reason to hold this PR again.

Merging this PR, and the publish that follows it, is the maintainer's act.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

⚠️ 152 changed file(s) yielded no anchor (packages/adapters/hono/CHANGELOG.md, packages/adapters/hono/package.json, packages/apps/account/CHANGELOG.md, …), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 76 changed package(s)).

What this run could not see

• 152 changed file(s) yielded no anchor (packages/adapters/hono/CHANGELOG.md, packages/adapters/hono/package.json, packages/apps/account/CHANGELOG.md, …) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 173 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 9f024d8a2c0776d12969ea25cee9b474be893e68 → packageMentionDocs.