Skip to content

chore: version packages#2042

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Closed

chore: version packages#2042
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm 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

@objectstack/cli@9.11.0

Minor Changes

  • c651f38: feat(cli): warn on unrecognized autonumber format tokens

    objectstack compile now flags autonumber formats whose {...} token is not a
    counter ({0000}), date ({YYYY}/{MM}/…) or {field} token — an unrecognized
    group (wrong case, spaces, punctuation, or a second sequence slot) renders
    LITERALLY into the record number, which is a silent footgun for AI-authored
    templates. Emitted as an advisory warning (autonumber-unrecognized-token),
    alongside the existing {field}-reference checks. The objectstack-data skill's
    field-types rules were also expanded to document the date/{field}/per-scope
    tokens and the authoring rules (required interpolated fields, delimited adjacent
    tokens, pad width is a minimum, date tokens are exact).

  • 36138c7: feat(autonumber): date, {field} and per-scope counter reset for autonumber formats

    autonumberFormat previously only understood a single {0000} sequence slot —
    everything else was a fixed literal prefix on one global counter. Real MES/eHR
    record numbers need three more token classes, so the format is now tokenized by a
    shared pure renderer in @objectstack/spec (parseAutonumberFormat /
    renderAutonumber) that the engine fallback and the SQL driver both call, so they
    emit byte-identical numbers (DB-native autonumber sequence (multi-instance correctness) #1603 parity):

    • Date tokens — {YYYY} {YY} {MM} {DD} {YYYYMMDD} resolve the calendar
      day in the request's business timezone (ExecutionContext.timezone, ADR-0053;
      UTC fallback), threaded through the new DriverOptions.timezone.
    • {field} interpolation — {section}{island_zone}{000} substitutes record
      field values into the prefix.
    • Per-scope counter reset — the counter's scope is the rendered prefix before
      the sequence slot, so AD{YYYYMMDD}{0000} resets daily, {section}{island_zone}{000}
      numbers per group, and {plan_no}{000} numbers per parent — all from one
      mechanism, no separate reset config.

    Fixed-prefix formats like CASE-{0000} render an empty scope and keep their single
    global counter, so existing sequences are unchanged. The persistent
    _objectstack_sequences table is keyed by a key_hash (SHA-256 of
    object, tenant_id, field, scope) — a single 64-char primary key that keys every
    dialect uniformly, stays within MySQL's utf8mb4 index-length limit (four raw
    columns would not), and lets scope be a generous non-indexed column. Deployments
    with an older table (3-column, or an interim scope column) are migrated in place
    on first use, carrying existing counters to scope=''.

    Guardrails:

    • Empty interpolated field is a hard error, not a silent mis-number. A
      {field} token whose value is missing at create time would render to an empty
      prefix and collapse the record into the wrong counter scope. Both the SQL driver
      and the engine fallback now refuse to generate and throw a clear error naming the
      empty field (shared missingFieldValues helper).
    • Build-time lint (@objectstack/cli compile). autonumber formats are
      checked against the object's fields: a {field} token naming a non-existent
      field (or the autonumber field itself) fails the build; a token naming an
      optional field emits an advisory warning to mark it required: true.
    • Migration fails safe. If a legacy table cannot be migrated to the key_hash
      shape, fixed-prefix sequences keep working via the legacy key and a per-scope
      write raises an actionable error instead of corrupting counters.
    • Long {field} scopes are supported (e.g. a long {plan_no}): the non-indexed
      scope column and hashed key remove the old varchar/PK length ceiling.

    Notes on inherent semantics (documented, not bugs):

    • The counter scope IS the rendered prefix. When two records' tokens render to the
      same prefix string (e.g. {a}{b} for ('AB','C') and ('A','BC')) they also
      render the same visible number, so they share one counter to stay unique — the
      remedy for genuinely-distinct groups is an unambiguous format (a delimiter
      literal between variable tokens).
    • The sequence pad width is a MINIMUM; past it the number grows ({000} →
      1000), it never wraps — matching mainstream autonumber semantics.

  • fd2e1a2: Add @objectstack/verify — boot any ObjectStack app in-process and verify it through the real HTTP stack: auto-derived CRUD round-trip fidelity (runCrudVerification) plus the cross-owner RLS invariant (runRlsProofs, "you can't write what you can't read"). Also adds an objectstack verify CLI command that runs these proofs against an app config and exits non-zero on real failures.

    Extracted from the internal dogfood regression gate so third-party and template authors can run the same runtime proofs against their own apps. The private @objectstack/dogfood package now consumes this library for its golden regression tests.

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [fd2e1a2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/driver-sql@9.11.0
    • @objectstack/plugin-security@9.11.0
    • @objectstack/verify@9.11.0
    • @objectstack/account@9.11.0
    • @objectstack/setup@9.11.0
    • @objectstack/studio@9.11.0
    • @objectstack/client@9.11.0
    • @objectstack/cloud-connection@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/mcp@9.11.0
    • @objectstack/observability@9.11.0
    • @objectstack/platform-objects@9.11.0
    • @objectstack/driver-memory@9.11.0
    • @objectstack/driver-mongodb@9.11.0
    • @objectstack/driver-sqlite-wasm@9.11.0
    • @objectstack/plugin-approvals@9.11.0
    • @objectstack/plugin-audit@9.11.0
    • @objectstack/plugin-auth@9.11.0
    • @objectstack/plugin-email@9.11.0
    • @objectstack/plugin-hono-server@9.11.0
    • @objectstack/plugin-org-scoping@9.11.0
    • @objectstack/plugin-reports@9.11.0
    • @objectstack/plugin-sharing@9.11.0
    • @objectstack/plugin-webhooks@9.11.0
    • @objectstack/rest@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/service-ai@9.11.0
    • @objectstack/service-analytics@9.11.0
    • @objectstack/service-automation@9.11.0
    • @objectstack/service-cache@9.11.0
    • @objectstack/service-datasource@9.11.0
    • @objectstack/service-job@9.11.0
    • @objectstack/service-messaging@9.11.0
    • @objectstack/service-package@9.11.0
    • @objectstack/service-queue@9.11.0
    • @objectstack/service-realtime@9.11.0
    • @objectstack/service-settings@9.11.0
    • @objectstack/service-storage@9.11.0
    • @objectstack/trigger-api@9.11.0
    • @objectstack/trigger-record-change@9.11.0
    • @objectstack/trigger-schedule@9.11.0
    • @objectstack/types@9.11.0
    • @objectstack/console@9.11.0

@objectstack/objectql@9.11.0

Minor Changes

  • 36138c7: feat(autonumber): date, {field} and per-scope counter reset for autonumber formats

    autonumberFormat previously only understood a single {0000} sequence slot —
    everything else was a fixed literal prefix on one global counter. Real MES/eHR
    record numbers need three more token classes, so the format is now tokenized by a
    shared pure renderer in @objectstack/spec (parseAutonumberFormat /
    renderAutonumber) that the engine fallback and the SQL driver both call, so they
    emit byte-identical numbers (DB-native autonumber sequence (multi-instance correctness) #1603 parity):

    • Date tokens — {YYYY} {YY} {MM} {DD} {YYYYMMDD} resolve the calendar
      day in the request's business timezone (ExecutionContext.timezone, ADR-0053;
      UTC fallback), threaded through the new DriverOptions.timezone.
    • {field} interpolation — {section}{island_zone}{000} substitutes record
      field values into the prefix.
    • Per-scope counter reset — the counter's scope is the rendered prefix before
      the sequence slot, so AD{YYYYMMDD}{0000} resets daily, {section}{island_zone}{000}
      numbers per group, and {plan_no}{000} numbers per parent — all from one
      mechanism, no separate reset config.

    Fixed-prefix formats like CASE-{0000} render an empty scope and keep their single
    global counter, so existing sequences are unchanged. The persistent
    _objectstack_sequences table is keyed by a key_hash (SHA-256 of
    object, tenant_id, field, scope) — a single 64-char primary key that keys every
    dialect uniformly, stays within MySQL's utf8mb4 index-length limit (four raw
    columns would not), and lets scope be a generous non-indexed column. Deployments
    with an older table (3-column, or an interim scope column) are migrated in place
    on first use, carrying existing counters to scope=''.

    Guardrails:

    • Empty interpolated field is a hard error, not a silent mis-number. A
      {field} token whose value is missing at create time would render to an empty
      prefix and collapse the record into the wrong counter scope. Both the SQL driver
      and the engine fallback now refuse to generate and throw a clear error naming the
      empty field (shared missingFieldValues helper).
    • Build-time lint (@objectstack/cli compile). autonumber formats are
      checked against the object's fields: a {field} token naming a non-existent
      field (or the autonumber field itself) fails the build; a token naming an
      optional field emits an advisory warning to mark it required: true.
    • Migration fails safe. If a legacy table cannot be migrated to the key_hash
      shape, fixed-prefix sequences keep working via the legacy key and a per-scope
      write raises an actionable error instead of corrupting counters.
    • Long {field} scopes are supported (e.g. a long {plan_no}): the non-indexed
      scope column and hashed key remove the old varchar/PK length ceiling.

    Notes on inherent semantics (documented, not bugs):

    • The counter scope IS the rendered prefix. When two records' tokens render to the
      same prefix string (e.g. {a}{b} for ('AB','C') and ('A','BC')) they also
      render the same visible number, so they share one counter to stay unique — the
      remedy for genuinely-distinct groups is an unambiguous format (a delimiter
      literal between variable tokens).
    • The sequence pad width is a MINIMUM; past it the number grows ({000} →
      1000), it never wraps — matching mainstream autonumber semantics.

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/metadata-core@9.11.0
    • @objectstack/types@9.11.0

@objectstack/driver-sql@9.11.0

Minor Changes

  • 36138c7: feat(autonumber): date, {field} and per-scope counter reset for autonumber formats

    autonumberFormat previously only understood a single {0000} sequence slot —
    everything else was a fixed literal prefix on one global counter. Real MES/eHR
    record numbers need three more token classes, so the format is now tokenized by a
    shared pure renderer in @objectstack/spec (parseAutonumberFormat /
    renderAutonumber) that the engine fallback and the SQL driver both call, so they
    emit byte-identical numbers (DB-native autonumber sequence (multi-instance correctness) #1603 parity):

    • Date tokens — {YYYY} {YY} {MM} {DD} {YYYYMMDD} resolve the calendar
      day in the request's business timezone (ExecutionContext.timezone, ADR-0053;
      UTC fallback), threaded through the new DriverOptions.timezone.
    • {field} interpolation — {section}{island_zone}{000} substitutes record
      field values into the prefix.
    • Per-scope counter reset — the counter's scope is the rendered prefix before
      the sequence slot, so AD{YYYYMMDD}{0000} resets daily, {section}{island_zone}{000}
      numbers per group, and {plan_no}{000} numbers per parent — all from one
      mechanism, no separate reset config.

    Fixed-prefix formats like CASE-{0000} render an empty scope and keep their single
    global counter, so existing sequences are unchanged. The persistent
    _objectstack_sequences table is keyed by a key_hash (SHA-256 of
    object, tenant_id, field, scope) — a single 64-char primary key that keys every
    dialect uniformly, stays within MySQL's utf8mb4 index-length limit (four raw
    columns would not), and lets scope be a generous non-indexed column. Deployments
    with an older table (3-column, or an interim scope column) are migrated in place
    on first use, carrying existing counters to scope=''.

    Guardrails:

    • Empty interpolated field is a hard error, not a silent mis-number. A
      {field} token whose value is missing at create time would render to an empty
      prefix and collapse the record into the wrong counter scope. Both the SQL driver
      and the engine fallback now refuse to generate and throw a clear error naming the
      empty field (shared missingFieldValues helper).
    • Build-time lint (@objectstack/cli compile). autonumber formats are
      checked against the object's fields: a {field} token naming a non-existent
      field (or the autonumber field itself) fails the build; a token naming an
      optional field emits an advisory warning to mark it required: true.
    • Migration fails safe. If a legacy table cannot be migrated to the key_hash
      shape, fixed-prefix sequences keep working via the legacy key and a per-scope
      write raises an actionable error instead of corrupting counters.
    • Long {field} scopes are supported (e.g. a long {plan_no}): the non-indexed
      scope column and hashed key remove the old varchar/PK length ceiling.

    Notes on inherent semantics (documented, not bugs):

    • The counter scope IS the rendered prefix. When two records' tokens render to the
      same prefix string (e.g. {a}{b} for ('AB','C') and ('A','BC')) they also
      render the same visible number, so they share one counter to stay unique — the
      remedy for genuinely-distinct groups is an unambiguous format (a delimiter
      literal between variable tokens).
    • The sequence pad width is a MINIMUM; past it the number grows ({000} →
      1000), it never wraps — matching mainstream autonumber semantics.

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/plugin-security@9.11.0

Minor Changes

  • 4c213c2: Master-detail "controlled by parent" permissions (ADR-0055).

    A detail object can now declare sharingModel: 'controlled_by_parent': its read/write access is derived from its master record, with no authored RLS.

    • @objectstack/spec: controlled_by_parent added to the authorable object.sharingModel enum.
    • @objectstack/plugin-security: reads inject masterFK IN (accessible master ids) (resolved from the master's own RLS, reusing the existing filter machinery — zero RLS-compiler changes); by-id writes (insert/update/delete) to a detail now require edit access to its master, closing the fix(security)[P0]: enforce RLS on by-id writes — close member-edits-others'-records hole (#1985) #1994-class by-id hole for derived access.
    • @objectstack/verify: related-record topological synthesis — deriveCrudCases no longer skips objects with required relations; it builds the object dependency graph, orders it topologically, and threads real target ids, so relationship-dense objects (and the master-detail RLS proof) are verifiable. Honest blocked verdicts remain for required-reference cycles and external/missing targets.

    v1 limits (per ADR-0055): the accessible-master id set is unbounded (large-tenant scale is a documented future limit), and master-detail chains are single-level (not transitively traversed).

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/spec@9.11.0

Minor Changes

  • 36138c7: feat(autonumber): date, {field} and per-scope counter reset for autonumber formats

    autonumberFormat previously only understood a single {0000} sequence slot —
    everything else was a fixed literal prefix on one global counter. Real MES/eHR
    record numbers need three more token classes, so the format is now tokenized by a
    shared pure renderer in @objectstack/spec (parseAutonumberFormat /
    renderAutonumber) that the engine fallback and the SQL driver both call, so they
    emit byte-identical numbers (DB-native autonumber sequence (multi-instance correctness) #1603 parity):

    • Date tokens — {YYYY} {YY} {MM} {DD} {YYYYMMDD} resolve the calendar
      day in the request's business timezone (ExecutionContext.timezone, ADR-0053;
      UTC fallback), threaded through the new DriverOptions.timezone.
    • {field} interpolation — {section}{island_zone}{000} substitutes record
      field values into the prefix.
    • Per-scope counter reset — the counter's scope is the rendered prefix before
      the sequence slot, so AD{YYYYMMDD}{0000} resets daily, {section}{island_zone}{000}
      numbers per group, and {plan_no}{000} numbers per parent — all from one
      mechanism, no separate reset config.

    Fixed-prefix formats like CASE-{0000} render an empty scope and keep their single
    global counter, so existing sequences are unchanged. The persistent
    _objectstack_sequences table is keyed by a key_hash (SHA-256 of
    object, tenant_id, field, scope) — a single 64-char primary key that keys every
    dialect uniformly, stays within MySQL's utf8mb4 index-length limit (four raw
    columns would not), and lets scope be a generous non-indexed column. Deployments
    with an older table (3-column, or an interim scope column) are migrated in place
    on first use, carrying existing counters to scope=''.

    Guardrails:

    • Empty interpolated field is a hard error, not a silent mis-number. A
      {field} token whose value is missing at create time would render to an empty
      prefix and collapse the record into the wrong counter scope. Both the SQL driver
      and the engine fallback now refuse to generate and throw a clear error naming the
      empty field (shared missingFieldValues helper).
    • Build-time lint (@objectstack/cli compile). autonumber formats are
      checked against the object's fields: a {field} token naming a non-existent
      field (or the autonumber field itself) fails the build; a token naming an
      optional field emits an advisory warning to mark it required: true.
    • Migration fails safe. If a legacy table cannot be migrated to the key_hash
      shape, fixed-prefix sequences keep working via the legacy key and a per-scope
      write raises an actionable error instead of corrupting counters.
    • Long {field} scopes are supported (e.g. a long {plan_no}): the non-indexed
      scope column and hashed key remove the old varchar/PK length ceiling.

    Notes on inherent semantics (documented, not bugs):

    • The counter scope IS the rendered prefix. When two records' tokens render to the
      same prefix string (e.g. {a}{b} for ('AB','C') and ('A','BC')) they also
      render the same visible number, so they share one counter to stay unique — the
      remedy for genuinely-distinct groups is an unambiguous format (a delimiter
      literal between variable tokens).
    • The sequence pad width is a MINIMUM; past it the number grows ({000} →
      1000), it never wraps — matching mainstream autonumber semantics.

  • 4c213c2: Master-detail "controlled by parent" permissions (ADR-0055).

    A detail object can now declare sharingModel: 'controlled_by_parent': its read/write access is derived from its master record, with no authored RLS.

    • @objectstack/spec: controlled_by_parent added to the authorable object.sharingModel enum.
    • @objectstack/plugin-security: reads inject masterFK IN (accessible master ids) (resolved from the master's own RLS, reusing the existing filter machinery — zero RLS-compiler changes); by-id writes (insert/update/delete) to a detail now require edit access to its master, closing the fix(security)[P0]: enforce RLS on by-id writes — close member-edits-others'-records hole (#1985) #1994-class by-id hole for derived access.
    • @objectstack/verify: related-record topological synthesis — deriveCrudCases no longer skips objects with required relations; it builds the object dependency graph, orders it topologically, and threads real target ids, so relationship-dense objects (and the master-detail RLS proof) are verifiable. Honest blocked verdicts remain for required-reference cycles and external/missing targets.

    v1 limits (per ADR-0055): the accessible-master id set is unbounded (large-tenant scale is a documented future limit), and master-detail chains are single-level (not transitively traversed).

Patch Changes

  • a8e4f3b: Add the ADR-0054 "prove-it-runs" proof field + ratchet to the spec liveness gate. A live ledger entry may now carry a proof — a reference (<file>#<proof-id>) to a dogfood test that asserts the property's runtime behavior. A bound high-risk live property must carry a valid proof, validated statically by the liveness gate (the file exists and declares the matching @proof: tag). Four high-risk classes are bound this phase: field types (field.type), RLS (permission.rowLevelSecurity.using), flow nodes (flow.nodes.type), and analytics (dataset.dimensions.dateGranularity). The dataset metadata type is now governed (new liveness/dataset.json). The authoritative high-risk-class list lives in scripts/liveness/proof-registry.mts; see liveness/README.md.

@objectstack/verify@9.11.0

Minor Changes

  • 4c213c2: Master-detail "controlled by parent" permissions (ADR-0055).

    A detail object can now declare sharingModel: 'controlled_by_parent': its read/write access is derived from its master record, with no authored RLS.

    • @objectstack/spec: controlled_by_parent added to the authorable object.sharingModel enum.
    • @objectstack/plugin-security: reads inject masterFK IN (accessible master ids) (resolved from the master's own RLS, reusing the existing filter machinery — zero RLS-compiler changes); by-id writes (insert/update/delete) to a detail now require edit access to its master, closing the fix(security)[P0]: enforce RLS on by-id writes — close member-edits-others'-records hole (#1985) #1994-class by-id hole for derived access.
    • @objectstack/verify: related-record topological synthesis — deriveCrudCases no longer skips objects with required relations; it builds the object dependency graph, orders it topologically, and threads real target ids, so relationship-dense objects (and the master-detail RLS proof) are verifiable. Honest blocked verdicts remain for required-reference cycles and external/missing targets.

    v1 limits (per ADR-0055): the accessible-master id set is unbounded (large-tenant scale is a documented future limit), and master-detail chains are single-level (not transitively traversed).

  • a8e4f3b: bootStack gains an opt-in automation boot option. When set, it registers @objectstack/service-automation so the app's authored flows are pulled from the registry and POST /api/v1/automation/:name/trigger actually executes their nodes against the real in-process stack. This makes flow-node execution + variable wiring verifiable end-to-end (ADR-0054 Phase 2), mirroring the existing multiTenant opt-in. Default is false, so the standard boot stays lean for apps that don't exercise flows.

  • fd2e1a2: Add @objectstack/verify — boot any ObjectStack app in-process and verify it through the real HTTP stack: auto-derived CRUD round-trip fidelity (runCrudVerification) plus the cross-owner RLS invariant (runRlsProofs, "you can't write what you can't read"). Also adds an objectstack verify CLI command that runs these proofs against an app config and exits non-zero on real failures.

    Extracted from the internal dogfood regression gate so third-party and template authors can run the same runtime proofs against their own apps. The private @objectstack/dogfood package now consumes this library for its golden regression tests.

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/plugin-security@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/driver-sqlite-wasm@9.11.0
    • @objectstack/plugin-auth@9.11.0
    • @objectstack/plugin-hono-server@9.11.0
    • @objectstack/plugin-org-scoping@9.11.0
    • @objectstack/plugin-sharing@9.11.0
    • @objectstack/rest@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/service-analytics@9.11.0
    • @objectstack/service-automation@9.11.0
    • @objectstack/service-settings@9.11.0

@objectstack/express@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/fastify@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/hono@9.11.0

Patch Changes

  • @objectstack/plugin-hono-server@9.11.0
  • @objectstack/runtime@9.11.0
  • @objectstack/types@9.11.0

@objectstack/nestjs@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/nextjs@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/nuxt@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/sveltekit@9.11.0

Patch Changes

  • @objectstack/runtime@9.11.0

@objectstack/account@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/setup@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/studio@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/client@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/client-react@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/client@9.11.0
    • @objectstack/core@9.11.0

@objectstack/cloud-connection@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/types@9.11.0

@objectstack/connector-mcp@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/connector-openapi@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/connector-rest@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/connector-slack@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/core@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/formula@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/mcp@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/types@9.11.0

@objectstack/metadata@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/metadata-core@9.11.0
    • @objectstack/platform-objects@9.11.0
    • @objectstack/types@9.11.0
    • @objectstack/metadata-fs@9.11.0

@objectstack/metadata-core@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/metadata-fs@9.11.0

Patch Changes

  • @objectstack/metadata-core@9.11.0

@objectstack/observability@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/platform-objects@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/metadata-core@9.11.0

@objectstack/driver-memory@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/driver-mongodb@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/driver-sqlite-wasm@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/driver-sql@9.11.0
    • @objectstack/core@9.11.0

@objectstack/embedder-openai@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/knowledge-memory@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/service-knowledge@9.11.0

@objectstack/knowledge-ragflow@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/service-knowledge@9.11.0

@objectstack/plugin-approvals@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/metadata-core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-audit@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-auth@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0
    • @objectstack/types@9.11.0

@objectstack/plugin-dev@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/plugin-security@9.11.0
    • @objectstack/account@9.11.0
    • @objectstack/setup@9.11.0
    • @objectstack/studio@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/driver-memory@9.11.0
    • @objectstack/plugin-auth@9.11.0
    • @objectstack/plugin-hono-server@9.11.0
    • @objectstack/plugin-org-scoping@9.11.0
    • @objectstack/rest@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/service-i18n@9.11.0
    • @objectstack/types@9.11.0

@objectstack/plugin-email@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-hono-server@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/types@9.11.0

@objectstack/plugin-msw@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/types@9.11.0

@objectstack/plugin-org-scoping@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-reports@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-sharing@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/plugin-webhooks@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/service-messaging@9.11.0

@objectstack/rest@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/service-package@9.11.0

@objectstack/runtime@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/driver-sql@9.11.0
    • @objectstack/plugin-security@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/metadata@9.11.0
    • @objectstack/observability@9.11.0
    • @objectstack/driver-memory@9.11.0
    • @objectstack/driver-sqlite-wasm@9.11.0
    • @objectstack/plugin-auth@9.11.0
    • @objectstack/plugin-org-scoping@9.11.0
    • @objectstack/rest@9.11.0
    • @objectstack/service-cluster@9.11.0
    • @objectstack/service-i18n@9.11.0
    • @objectstack/types@9.11.0

@objectstack/service-ai@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0
    • @objectstack/types@9.11.0

@objectstack/service-analytics@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-automation@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/formula@9.11.0

@objectstack/service-cache@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/observability@9.11.0

@objectstack/service-cluster@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-cluster-redis@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/service-cluster@9.11.0

@objectstack/service-datasource@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-i18n@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-job@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/service-knowledge@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-messaging@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-package@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/service-queue@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/service-realtime@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/service-settings@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/platform-objects@9.11.0
    • @objectstack/types@9.11.0

@objectstack/service-storage@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0
    • @objectstack/observability@9.11.0
    • @objectstack/platform-objects@9.11.0

@objectstack/trigger-api@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/trigger-record-change@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/trigger-schedule@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/core@9.11.0

@objectstack/types@9.11.0

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0

@objectstack/console@9.11.0

create-objectstack@9.11.0

objectstack-vscode@9.11.0

@objectstack/example-crm@4.0.54

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/runtime@9.11.0

@objectstack/example-showcase@0.1.24

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/cloud-connection@9.11.0
    • @objectstack/connector-rest@9.11.0
    • @objectstack/connector-slack@9.11.0
    • @objectstack/runtime@9.11.0

@objectstack/example-todo@4.0.54

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/client@9.11.0
    • @objectstack/metadata@9.11.0
    • @objectstack/driver-sqlite-wasm@9.11.0
    • @objectstack/knowledge-memory@9.11.0
    • @objectstack/runtime@9.11.0
    • @objectstack/service-ai@9.11.0
    • @objectstack/service-knowledge@9.11.0

@objectstack/dogfood@0.0.2

Patch Changes

  • Updated dependencies [36138c7]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [4c213c2]
  • Updated dependencies [a8e4f3b]
  • Updated dependencies [fd2e1a2]
    • @objectstack/spec@9.11.0
    • @objectstack/objectql@9.11.0
    • @objectstack/plugin-security@9.11.0
    • @objectstack/verify@9.11.0
    • @objectstack/example-crm@4.0.54
    • @objectstack/example-showcase@0.1.24

@vercel

vercel Bot commented Jun 19, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
spec Ready Ready Preview, Comment Jun 20, 2026 5:09am

Request Review

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from abf2ffe to d1f7e4f Compare June 19, 2026 09:13
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d1f7e4f to c7bd0e8 Compare June 19, 2026 10:17
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c7bd0e8 to 66950b6 Compare June 19, 2026 11:03
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 66950b6 to c8a6107 Compare June 19, 2026 11:11
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c8a6107 to 5496aad Compare June 19, 2026 13:44
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5496aad to 9a158a2 Compare June 19, 2026 14:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9a158a2 to f9da556 Compare June 19, 2026 15:07
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from f9da556 to 91d164d Compare June 19, 2026 16:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 91d164d to 28c1d4f Compare June 20, 2026 01:22
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 28c1d4f to 3ddf6e9 Compare June 20, 2026 04:20
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3ddf6e9 to ba64838 Compare June 20, 2026 04:47
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ba64838 to e4a1f2e Compare June 20, 2026 05:05
@os-zhuang os-zhuang closed this Jun 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@os-zhuang