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 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/studio@5.2.0

Minor Changes

• fa011d8: feat(studio): metadata history timeline viewer

  Adds a new history view mode that surfaces the audit timeline produced by sys_metadata_history (ADR-0008 §5) inside Studio. Available for every metadata type as a wildcard built-in plugin.

  • @objectstack/spec: extend ViewModeSchema with 'history'.
  • @objectstack/studio: new historyViewerPlugin rendering an event timeline (create/update/delete/rename) with op icons, short hash, actor, source, expandable detail panel. ADR-0009 executionPinned types (flow, workflow, approval) show a "Pinned" badge explaining that historical versions are retained for in-flight executions.

  Reads from the existing GET /meta/:type/:name/history REST endpoint via client.meta.getHistory(); no new server surface.

Patch Changes

• 7bc57ad: Studio: redesign the object page Airtable-style.

  The object detail page (/objects/:name) previously stacked four
  overlapping navigation strips on top of each other: sidebar, outer
  route tabs (Designer/Views/Forms/...), the PluginHost mode strip
  (Preview/Code/Data/History), and ObjectExplorer's own internal
  tabs (Schema/Data/API) — plus a duplicated object header card.

  This change collapses the redundancy:

  • ObjectExplorer becomes a controlled component driven by the
    mode prop from PluginHost. Its internal tab strip is removed
    so the page only ever shows a single row of mode buttons.
  • The duplicate "object meta" card inside ObjectSchemaInspector
    is removed; the route-level header is now the single source of
    identity (label + machine name + description).
  • The route header itself is slimmed: the "Object" eyebrow and
    the redundant stat-badge row (fields / views / forms / hooks)
    are gone since the related-metadata tabs already convey the
    same counts.
  • object-plugin declares modes as ['data', 'design', 'code']
    and PluginHost lands on data by default for objects so the
    records grid is the first thing the user sees — matching
    Airtable's "data first" philosophy.
  • Mode buttons get per-type labels via MODE_LABEL_OVERRIDES:
    for object, data reads "Records", design reads "Fields",
    code reads "API".
  • A per-type MODE_ALLOWLIST_BY_TYPE filters out the generic
    preview fallback for objects so the strip is the curated
    Records / Fields / API / History and nothing more.

• ec26370: Studio: cross-page polish — calmer cards, plain-English copy, deduped registry.

  Following the Airtable-style object-page redesign, this pass cleans
  up the rest of the surface so every page reads the same way.

  List cards (MetadataListPage):

  • Suppress the per-card type badge on single-type pages (Objects,
    Forms). The page title already conveys the type; the badge was
    noise. Multi-type pages (Views & Apps, Automations, AI, Security)
    keep the badge for disambiguation.
  • Show the metadata's own description when present, instead of
    the now-redundant snake_case name (which was a duplicate of the
    <code> element below). The machine name still appears as a
    subtle code line.
  • Switch the "Preview" verbose button to an icon-only ghost button
    that reveals on hover, freeing the row for the actual label.
  • Add title attributes everywhere so truncated labels (e.g.
    "Campaign Me…") are readable on hover.

  Home / DeveloperOverview:

  • Replace the "Developer Console" terminal-icon header with the
    package name and a one-line summary — feels like a product home,
    not a dev tool.
  • Dedupe the Metadata Registry list: the backend currently exposes
    both sharingRule and sharing_rule (and ragPipeline /
    rag_pipeline, analyticsCube / analytics_cube) as separate
    entries even though they map to the same type. A new
    dedupeRegistryEntries collapses each alias pair, sums the
    counts, and keeps the canonical camelCase name for display.
  • Drop the "+ N empty types" footnote — pure dev jargon.
  • Replace the opaque /api/v1 REST · data · meta · packages
    stat card with a clearer "REST API — Live" card that links to
    the APIs page.

  Forms:

  • Rewrite the page description from a wall of
    FormView / sharing.allowAnonymous / GET /api/v1/forms/:slug
    jargon to plain English: "Forms anyone can fill out — no login
    required. Publish a form to get a shareable link; submissions
    land directly in the bound object."
  • Empty state now points users at the visible action button
    instead of telling them to "Declare a FormView with
    sharing.allowAnonymous: true".

  Logs:

  • Empty states no longer leak the internal endpoint paths
    (Awaiting /api/v1/_debug/requests.) — they just say
    "Coming soon. Requests will stream here in real time."

• b626e11: Studio: redesign generic metadata-detail pages.

  Every detail page routed through /$package/metadata/$type/$name
  (views, dashboards, apps, flows, agents, permissions, …) used to
  have no visible page header — only a breadcrumb — plus a
  wasted top band hosting a floating 3-dot menu, a dev-jargon
  objectstack.view-preview plugin-id badge, and an unnecessary
  viewer-picker dropdown. Errors were rendered as red prose leaking
  the raw [ObjectStack] Metadata item X not found backend string.

  This pass aligns generic detail pages with the Object-page pattern:

  • The route now loads the item, renders a real header card
    (icon · label · machine name · type chip · description), and
    parks the ResourceActionsMenu on the right of the header
    instead of in its own floating top bar.
  • PluginHost drops the always-visible plugin-id badge from the
    toolbar (objectstack.view-preview etc. — pure dev jargon)
    and the same id badge from inside the viewer-picker dropdown
    items.
  • MetadataInspector (the default JSON-tree Preview viewer) no
    longer renders its own "Header card" — that's the route's job
    now, so users don't see "Sales Representative" twice on the
    Permission page.
  • Friendly "not found" empty states replace the red error prose
    in view-preview-plugin, FlowViewer, and MetadataInspector.
    Internal error strings like
    [ObjectStack] Metadata item flow/X not found no longer leak
    to the UI; users see "Flow not found · We couldn't load X. It
    may have been deleted or moved to another package."

• d060e84: fix(studio): clearer metadata list filter chips, empty states & no-flash theme boot

  Surveyed Studio's core pages via the browser and shipped three targeted polish fixes:

  • Filter chips on multi-type list pages (Views & Apps, Automations, …) were displaying the nav-category label for every chip — e.g. "Views & Apps 1" / "Views & Apps 2" instead of "App 1" / "Dashboard 2". Added a singular METADATA_TYPE_LABELS registry and a typeLabel() helper in studio-nav.ts, and switched the chip + search placeholder + empty-state copy to per-type labels.
  • Empty-state grammar: "No ai in this package yet." now reads "Nothing in AI for this package yet." — works for any title casing (AI, Views & Apps, …) without lowercasing.
  • First-paint theme flash: stored theme was only applied in a useEffect, causing a brief white flash before React mounted (especially noticeable on slow loads). Added an inline <script> in index.html that mirrors theme-toggle.tsx and applies the .dark class and the matching <html> background-color synchronously, plus a <meta name="color-scheme" content="dark light"> so native UI (scrollbars, form controls) inherits the correct scheme too.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [f0f7c27]

• Updated dependencies [b806f58]

  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/runtime@5.2.0
  • @objectstack/metadata@5.2.0
  • @objectstack/service-ai@5.2.0
  • @objectstack/client@5.2.0
  • @objectstack/client-react@5.2.0
  • @objectstack/objectql@5.2.0
  • @objectstack/driver-memory@5.2.0
  • @objectstack/plugin-msw@5.2.0
  • @objectstack/service-analytics@5.2.0
  • @objectstack/service-automation@5.2.0
  • @objectstack/service-feed@5.2.0

@objectstack/platform-objects@5.2.0

Minor Changes

• bab2b20: feat(approvals): execution-pinned approval processes (ADR-0009)

  When an approval request is submitted, the engine now records a process_hash
  on sys_approval_request — the sha256 of the approval process body resolved
  through MetadataRepository. While the request is in flight, approve /
  reject / recall resolve the pinned process body via
  MetadataRepository.getByHash. Upgrading the approval process definition
  mid-flight therefore no longer affects requests that already started against
  the previous version.

  Behavior:

  • sys_approval_request gains a process_hash column (text, nullable,
    read-only). Existing rows keep working — the engine falls back to the
    current sys_approval_process projection when the column is empty.
  • ApprovalServiceOptions accepts an optional metadataRepo. When omitted
    (e.g. defining processes purely through the runtime API or in unit tests),
    pinning is silently disabled and the service behaves as before.
  • ApprovalsServicePlugin looks up the metadata service from the kernel
    and wires its repository automatically.
  • The metadata-core local MetadataTypeSchema enum was realigned with the
    canonical @objectstack/spec/kernel enum (drift fix: approval, field,
    function, service, …).

  This is the first user-visible consumer of the executionPinned capability
  introduced in ADR-0009.

Patch Changes

• f0f7c27: Add mark_read / mark_unread row actions to sys_notification and polish
  listView columns + grouping.

  • Row-level mark_read / mark_unread actions guarded by CEL visible
    expressions so each only renders on rows in the appropriate state. Both
    use the generic PATCH /api/v1/data/sys_notification/{id} endpoint with
    bodyExtra to flip is_read (and clear read_at on unmark).
  • Reordered listView columns to lead with title + actor_name (the "who
    did what" users actually scan) and demote type to a chip column.
  • mine view now groups by type so mention/assignment storms don't bury
    system or task_due rows.

  mark_all_read is intentionally not added server-side — there's no bulk
  PATCH primitive on the REST surface yet, and the popover already handles
  multi-row mark-all client-side via N single-row PATCHes
  (InboxPopover.tsx → AppHeader.markAllRead).

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [b806f58]

  • @objectstack/spec@5.2.0

@objectstack/plugin-approvals@5.2.0

Minor Changes

• bab2b20: feat(approvals): execution-pinned approval processes (ADR-0009)

  When an approval request is submitted, the engine now records a process_hash
  on sys_approval_request — the sha256 of the approval process body resolved
  through MetadataRepository. While the request is in flight, approve /
  reject / recall resolve the pinned process body via
  MetadataRepository.getByHash. Upgrading the approval process definition
  mid-flight therefore no longer affects requests that already started against
  the previous version.

  Behavior:

  • sys_approval_request gains a process_hash column (text, nullable,
    read-only). Existing rows keep working — the engine falls back to the
    current sys_approval_process projection when the column is empty.
  • ApprovalServiceOptions accepts an optional metadataRepo. When omitted
    (e.g. defining processes purely through the runtime API or in unit tests),
    pinning is silently disabled and the service behaves as before.
  • ApprovalsServicePlugin looks up the metadata service from the kernel
    and wires its repository automatically.
  • The metadata-core local MetadataTypeSchema enum was realigned with the
    canonical @objectstack/spec/kernel enum (drift fix: approval, field,
    function, service, …).

  This is the first user-visible consumer of the executionPinned capability
  introduced in ADR-0009.

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/metadata-core@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/formula@5.2.0

@objectstack/spec@5.2.0

Minor Changes

• fa011d8: feat(studio): metadata history timeline viewer

  Adds a new history view mode that surfaces the audit timeline produced by sys_metadata_history (ADR-0008 §5) inside Studio. Available for every metadata type as a wildcard built-in plugin.

  • @objectstack/spec: extend ViewModeSchema with 'history'.
  • @objectstack/studio: new historyViewerPlugin rendering an event timeline (create/update/delete/rename) with op icons, short hash, actor, source, expandable detail panel. ADR-0009 executionPinned types (flow, workflow, approval) show a "Pinned" badge explaining that historical versions are retained for in-flight executions.

  Reads from the existing GET /meta/:type/:name/history REST endpoint via client.meta.getHistory(); no new server surface.

Patch Changes

• bab2b20: feat(approvals): execution-pinned approval processes (ADR-0009)

  When an approval request is submitted, the engine now records a process_hash
  on sys_approval_request — the sha256 of the approval process body resolved
  through MetadataRepository. While the request is in flight, approve /
  reject / recall resolve the pinned process body via
  MetadataRepository.getByHash. Upgrading the approval process definition
  mid-flight therefore no longer affects requests that already started against
  the previous version.

  Behavior:

  • sys_approval_request gains a process_hash column (text, nullable,
    read-only). Existing rows keep working — the engine falls back to the
    current sys_approval_process projection when the column is empty.
  • ApprovalServiceOptions accepts an optional metadataRepo. When omitted
    (e.g. defining processes purely through the runtime API or in unit tests),
    pinning is silently disabled and the service behaves as before.
  • ApprovalsServicePlugin looks up the metadata service from the kernel
    and wires its repository automatically.
  • The metadata-core local MetadataTypeSchema enum was realigned with the
    canonical @objectstack/spec/kernel enum (drift fix: approval, field,
    function, service, …).

  This is the first user-visible consumer of the executionPinned capability
  introduced in ADR-0009.

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

@objectstack/account@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/client@5.2.0
  • @objectstack/client-react@5.2.0

@objectstack/hono@5.2.0

Patch Changes

• Updated dependencies [b806f58]
  • @objectstack/plugin-hono-server@5.2.0

@objectstack/cli@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/plugin-approvals@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/runtime@5.2.0
  • @objectstack/plugin-security@5.2.0
  • @objectstack/plugin-hono-server@5.2.0
  • @objectstack/rest@5.2.0
  • @objectstack/plugin-audit@5.2.0
  • @objectstack/plugin-auth@5.2.0
  • @objectstack/plugin-email@5.2.0
  • @objectstack/plugin-reports@5.2.0
  • @objectstack/plugin-sharing@5.2.0
  • @objectstack/service-ai@5.2.0
  • @objectstack/service-job@5.2.0
  • @objectstack/service-queue@5.2.0
  • @objectstack/service-realtime@5.2.0
  • @objectstack/service-settings@5.2.0
  • @objectstack/client@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/objectql@5.2.0
  • @objectstack/driver-memory@5.2.0
  • @objectstack/driver-mongodb@5.2.0
  • @objectstack/driver-sql@5.2.0
  • @objectstack/driver-turso@5.2.0
  • @objectstack/plugin-mcp-server@5.2.0
  • @objectstack/service-analytics@5.2.0
  • @objectstack/service-automation@5.2.0
  • @objectstack/service-cache@5.2.0
  • @objectstack/service-feed@5.2.0
  • @objectstack/service-package@5.2.0
  • @objectstack/service-storage@5.2.0

@objectstack/client@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/client-react@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/client@5.2.0
  • @objectstack/core@5.2.0

@objectstack/core@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0

@objectstack/formula@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0

@objectstack/metadata@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/metadata-core@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/types@5.2.0
  • @objectstack/metadata-fs@5.2.0

@objectstack/metadata-core@5.2.0

Patch Changes

• bab2b20: feat(approvals): execution-pinned approval processes (ADR-0009)

  When an approval request is submitted, the engine now records a process_hash
  on sys_approval_request — the sha256 of the approval process body resolved
  through MetadataRepository. While the request is in flight, approve /
  reject / recall resolve the pinned process body via
  MetadataRepository.getByHash. Upgrading the approval process definition
  mid-flight therefore no longer affects requests that already started against
  the previous version.

  Behavior:

  • sys_approval_request gains a process_hash column (text, nullable,
    read-only). Existing rows keep working — the engine falls back to the
    current sys_approval_process projection when the column is empty.
  • ApprovalServiceOptions accepts an optional metadataRepo. When omitted
    (e.g. defining processes purely through the runtime API or in unit tests),
    pinning is silently disabled and the service behaves as before.
  • ApprovalsServicePlugin looks up the metadata service from the kernel
    and wires its repository automatically.
  • The metadata-core local MetadataTypeSchema enum was realigned with the
    canonical @objectstack/spec/kernel enum (drift fix: approval, field,
    function, service, …).

  This is the first user-visible consumer of the executionPinned capability
  introduced in ADR-0009.

@objectstack/metadata-fs@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
  • @objectstack/metadata-core@5.2.0

@objectstack/objectql@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/metadata-core@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/formula@5.2.0
  • @objectstack/types@5.2.0

@objectstack/observability@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0

@objectstack/driver-memory@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/driver-mongodb@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/driver-sql@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/driver-turso@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/driver-sql@5.2.0

@objectstack/plugin-audit@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-auth@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-dev@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-email@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-hono-server@5.2.0

Patch Changes

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [b806f58]

  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-mcp-server@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-msw@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/objectql@5.2.0
  • @objectstack/types@5.2.0

@objectstack/plugin-reports@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-security@5.2.0

Patch Changes

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [f0f7c27]

• Updated dependencies [b806f58]

  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/plugin-sharing@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/objectql@5.2.0

@objectstack/plugin-webhooks@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/rest@5.2.0

Patch Changes

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [b806f58]

  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/service-package@5.2.0

@objectstack/runtime@5.2.0

Patch Changes

• b806f58: Scope sys_user visibility to fellow organization members.

  The default RLS policy on sys_user was id = current_user.id, which meant
  @-mention pickers, owner/assignee lookups, reviewer selectors and the user
  roster all returned just the current user. The RLS compiler doesn't support
  subqueries, so a id IN (SELECT user_id FROM sys_member ...) policy isn't
  expressible.

  This change:

  1. Pre-resolves org_user_ids (the IDs of all users in the active org) into
     ExecutionContext in all three REST entry-point resolvers
     (@objectstack/rest, @objectstack/runtime, @objectstack/plugin-hono-server).
  2. Adds the field to ExecutionContextSchema so it survives Zod parsing.
  3. Adds an org_user_ids field to the RLS compiler's user context.
  4. Adds a new sys_user_org_members policy (id IN (current_user.org_user_ids))
     to both member_default and viewer_readonly permission sets, alongside
     the existing sys_user_self policy. The RLS compiler OR-combines them, so
     users see themselves AND their org collaborators.

  Capped at 1000 members per request. Large enterprises should plug in a
  directory cache or split per workspace.

• Updated dependencies [bab2b20]

• Updated dependencies [fa011d8]

• Updated dependencies [b806f58]

  • @objectstack/spec@5.2.0
  • @objectstack/plugin-security@5.2.0
  • @objectstack/rest@5.2.0
  • @objectstack/plugin-auth@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/formula@5.2.0
  • @objectstack/observability@5.2.0
  • @objectstack/service-i18n@5.2.0
  • @objectstack/types@5.2.0

@objectstack/service-ai@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-analytics@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-automation@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/formula@5.2.0

@objectstack/service-cache@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/observability@5.2.0

@objectstack/service-feed@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-i18n@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-job@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-package@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-queue@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-realtime@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-settings@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [f0f7c27]
• Updated dependencies [b806f58]
  • @objectstack/platform-objects@5.2.0
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0

@objectstack/service-storage@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/core@5.2.0
  • @objectstack/observability@5.2.0

@objectstack/types@5.2.0

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0

@objectstack/console@5.2.0

@objectstack/express@5.2.0

@objectstack/fastify@5.2.0

@objectstack/nestjs@5.2.0

@objectstack/nextjs@5.2.0

@objectstack/nuxt@5.2.0

@objectstack/sveltekit@5.2.0

create-objectstack@5.2.0

objectstack-vscode@5.2.0

@objectstack/example-crm@4.0.11

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/runtime@5.2.0
  • @objectstack/driver-mongodb@5.2.0
  • @objectstack/service-analytics@5.2.0
  • @objectstack/service-automation@5.2.0

@example/app-todo@4.0.11

Patch Changes

• Updated dependencies [bab2b20]
• Updated dependencies [fa011d8]
• Updated dependencies [b806f58]
  • @objectstack/spec@5.2.0
  • @objectstack/runtime@5.2.0
  • @objectstack/client@5.2.0
  • @objectstack/objectql@5.2.0
  • @objectstack/driver-memory@5.2.0

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	May 23, 2026 5:34am