chore: version packages

[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/console@18.0.0

@objectstack/lint@18.0.0

@objectstack/metadata-protocol@18.0.0

@objectstack/objectql@18.0.0

@objectstack/plugin-security@18.0.0

@objectstack/service-automation@18.0.0

@objectstack/spec@18.0.0

@objectstack/trigger-api@18.0.0

@objectstack/hono@18.0.0

@objectstack/cli@18.0.0

@objectstack/client@18.0.0

@objectstack/cloud-connection@18.0.0

@objectstack/connector-imap@18.0.0

@objectstack/connector-mcp@18.0.0

@objectstack/core@18.0.0

create-objectstack@18.0.0

@objectstack/driver-memory@18.0.0

@objectstack/driver-mongodb@18.0.0

@objectstack/driver-sql@18.0.0

@objectstack/driver-sqlite-wasm@18.0.0

@objectstack/driver-turso@18.0.0

@objectstack/formula@18.0.0

@objectstack/mcp@18.0.0

@objectstack/metadata@18.0.0

@objectstack/metadata-core@18.0.0

@objectstack/platform-objects@18.0.0

@objectstack/plugin-approvals@18.0.0

@objectstack/plugin-audit@18.0.0

@objectstack/plugin-auth@18.0.0

@objectstack/plugin-dev@18.0.0

@objectstack/plugin-email@18.0.0

@objectstack/plugin-hono-server@18.0.0

@objectstack/plugin-sharing@18.0.0

@objectstack/plugin-webhooks@18.0.0

@objectstack/rest@18.0.0

@objectstack/runtime@18.0.0

@objectstack/service-analytics@18.0.0

@objectstack/service-datasource@18.0.0

@objectstack/service-i18n@18.0.0

@objectstack/service-mailbox@18.0.0

@objectstack/service-messaging@18.0.0

@objectstack/service-package@18.0.0

@objectstack/service-print@18.0.0

@objectstack/service-realtime@18.0.0

@objectstack/service-settings@18.0.0

@objectstack/service-sms@18.0.0

@objectstack/service-storage@18.0.0

@objectstack/skills@18.0.0

@objectstack/types@18.0.0

@objectstack/verify@18.0.0

@objectstack/account@18.0.0

@objectstack/setup@18.0.0

@objectstack/studio@18.0.0

@objectstack/client-react@18.0.0

@objectstack/connector-openapi@18.0.0

@objectstack/connector-rest@18.0.0

@objectstack/connector-slack@18.0.0

@objectstack/metadata-fs@18.0.0

@objectstack/observability@18.0.0

@objectstack/embedder-openai@18.0.0

@objectstack/knowledge-memory@18.0.0

@objectstack/knowledge-ragflow@18.0.0

@objectstack/organizations@18.0.0

@objectstack/plugin-pinyin-search@18.0.0

@objectstack/service-cache@18.0.0

@objectstack/service-cluster@18.0.0

@objectstack/service-cluster-redis@18.0.0

@objectstack/service-job@18.0.0

@objectstack/service-knowledge@18.0.0

@objectstack/service-queue@18.0.0

@objectstack/trigger-record-change@18.0.0

@objectstack/trigger-schedule@18.0.0

@objectstack/sdui-parser@18.0.0

@objectstack/example-crm@4.0.100

@objectstack/example-multi-package@0.0.7

@objectstack/example-showcase@0.3.22

@objectstack/example-todo@4.0.100

@objectstack/example-embed-objectql@0.0.40

@objectstack/dogfood@0.0.48

@objectstack/downstream-contract@0.0.46

@objectstack/http-conformance@0.1.8

[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 973917c5795f7a440d46a15bc5cf8961af9d8703 → packageMentionDocs.