@objectstack/client

16.1.1

Patch Changes

@objectstack/spec@16.1.1
@objectstack/core@16.1.1

16.1.0

Patch Changes

Updated dependencies [9e45b63]
Updated dependencies [b20201f]
- @objectstack/spec@16.1.0
- @objectstack/core@16.1.0

16.0.0

Minor Changes

9ccd1e9: feat(client): typed data.batchTransaction() for the atomic cross-object batch (#1604 / ADR-0034 item 4)

Adds client.data.batchTransaction(operations) (and the environment-scoped client.project(id).data.batchTransaction) — a typed SDK surface for POST {basePath}/batch, the all-or-nothing cross-object transactional batch that master-detail saves go through. Reuses CrossObjectBatchOperation / CrossObjectBatchRequest / CrossObjectBatchResponse from @objectstack/spec/api (also re-exported from the client for convenience); supports { $ref: <opIndex> } intra-batch parent references.

The method is always atomic and deliberately exposes no atomic flag — the endpoint rejects atomic: false with 400 BATCH_NOT_ATOMIC. Non-atomic per-object bulk writes stay on data.batch() / createMany / updateMany, so any best-effort fallback is isolated in the caller's adapter (the ObjectUI masterDetailTx adapter), not in the SDK.
bfa3c3f: Broadcast a transactionalBatch capability bit in discovery so clients negotiate the atomic cross-object batch declaratively, instead of runtime-probing 404/405/501 (#3298).

The atomic cross-object batch endpoint (POST {basePath}/batch, #1604 / ADR-0034 item 4) and its typed SDK surface (client.data.batchTransaction, #3271) already shipped, but discovery never told a client whether a backend actually supports it. Consumers (notably ObjectUI's ObjectStackAdapter) had to probe: fire a /batch, read 404/405 (no route) or 501 (no runtime transaction), and only then fall back to non-atomic client-side simulation. That is "find out by calling", not capability negotiation — it cannot be decided at connect time and cannot serve as the "minimum backend supports /batch" gate that blocks hard-deleting the non-atomic fallback downstream.

WellKnownCapabilitiesSchema gains a required transactionalBatch: boolean, and every discovery producer fills it honestly (declared === enforced), so it never becomes a declared-but-unpopulated bit:
- @objectstack/metadata-protocol (getDiscovery) — reports whether the runtime engine can honour a transaction (typeof engine.transaction === 'function'). The /batch handler runs its ops inside engine.transaction(), which degrades to a non-atomic passthrough (or 501) without one.
- @objectstack/rest (/discovery) — ANDs the engine signal with whether it actually mounts the route (api.enableBatch), so a server with batch disabled reports false even on a transaction-capable engine (never advertise an endpoint that would 404).
- @objectstack/plugin-hono-server (standalone discovery) — reports false: this minimal surface registers CRUD only and does not mount /batch (that ships with @objectstack/rest). Under-reporting is the safe direction — a client keeps its correct-but-slower fallback rather than losing atomicity.
- @objectstack/client — already normalizes hierarchical capabilities to flat booleans, so client.capabilities.transactionalBatch is exposed (and now typed) for declarative consumers.
The bit follows the existing capability semantics: true ⟺ the /batch route is mounted and the runtime can honour a transaction — the exact condition under which the endpoint returns 200 rather than 404/405/501. Additive and behavior-preserving; only the discovery payload gains a field.
668dd17: Breaking (npm type surface): retire the vestigial feed contracts + protocol surface (ADR-0052 §5 follow-up, #1959).

The service-feed runtime was deleted in #1955; sys_comment / sys_activity are the canonical record-collaboration/timeline backend. This removes the dead type surface that still pointed at the deleted runtime — every removed method was already unreachable (the feed REST route was never mounted → 404; the protocol implementation was never wired with a feed service, so requireFeedService() could only throw). No behavior changes.

No authorable metadata key is removed (the feeds: object capability flag and the RecordActivity UI component config are unchanged), so PROTOCOL_MAJOR stays 15 and this ships as minor rather than a protocol major.

FROM → TO migration for every removed export:
- @objectstack/spec/contracts — IFeedService, CreateFeedItemInput, UpdateFeedItemInput, ListFeedOptions, FeedListResult → removed, no replacement. Comments/activity are plain records: write sys_comment / read sys_activity via the data engine or the REST data API.
- @objectstack/spec/api — FeedApiContracts, FeedApiErrorCode, FeedProtocol, and all feed request/response schemas + types (GetFeed*, CreateFeedItem*, UpdateFeedItem*, DeleteFeedItem*, AddReaction*, RemoveReaction*, PinFeedItem*, UnpinFeedItem*, StarFeedItem*, UnstarFeedItem*, SearchFeed*, GetChangelog*, ChangelogEntry, SubscribeRequest/Response, FeedUnsubscribeRequest, UnsubscribeResponse, FeedPathParams, FeedItemPathParams, FeedListFilterType) → removed. Use the data API against sys_comment / sys_activity (/api/v1/data/sys_comment/…); reactions and threaded replies are fields on sys_comment.
- @objectstack/spec/data — FeedItemSchema/FeedItem, FeedActorSchema/FeedActor, MentionSchema/Mention, ReactionSchema/Reaction, FieldChangeEntrySchema/FieldChangeEntry, FeedVisibility, RecordSubscriptionSchema/RecordSubscription, SubscriptionEventType, and the data-namespace NotificationChannel → removed. FeedItemType and FeedFilterMode are kept (live UI activity-timeline config). For notification channels use NotificationChannelSchema from @objectstack/spec/system.
- @objectstack/client — client.feed.* (list / create / update / delete / addReaction / removeReaction / pin / unpin / star / unstar / search / getChangelog / subscribe / unsubscribe) and the re-exported feed response types → removed. One-line fix: use client.data.* on sys_comment / sys_activity, e.g. client.data.create('sys_comment', { object, record_id, body }) and client.data.find('sys_activity', { filters: [['record_id', '=', id]] }).
- @objectstack/metadata-protocol — ObjectStackProtocolImplementation no longer implements the 14 feed methods; its constructor (engine, getServicesRegistry?, getFeedService?, environmentId?) becomes (engine, getServicesRegistry?, environmentId?). One-line fix: delete the third argument.

Patch Changes

8abf133: Breaking (discovery response shape): retire the residual feed capability surface (#3180, follow-up to #1959 / ADR-0052 §5).

The feed backend was retired long ago; #1959 removed the feed contracts + SDK. This removes the last discovery/dispatcher references to it, and fixes a real bug where the comments capability was permanently false.
- @objectstack/spec — WellKnownCapabilitiesSchema.feed and ApiRoutesSchema.feed (routes.feed) are removed, and the /api/v1/feed entry is dropped from DEFAULT_DISPATCHER_ROUTES. FROM → TO: clients reading discovery.capabilities.feed or discovery.routes.feed → use discovery.capabilities.comments; comments/activity are served by the generic data API on sys_comment / sys_activity (/api/v1/data/sys_comment/…).
- @objectstack/metadata-protocol — getDiscovery() no longer emits the always-false feed service/capability. Bug fix: the comments capability previously keyed off the deleted 'feed' service (so it was permanently false after #1955); it now tracks the presence of the sys_comment object (provided by the always-on audit slate), so declared === enforced.
- @objectstack/client — the internal feed: '/api/v1/feed' route constant is removed (it only existed to satisfy the now-removed ApiRoutes.feed type; no client code used it).
Updated dependencies [f972574]
Updated dependencies [6289ec3]
Updated dependencies [22013aa]
Updated dependencies [3ad3dd5]
Updated dependencies [8efa395]
Updated dependencies [3a18b60]
Updated dependencies [a8aa34c]
Updated dependencies [e057f42]
Updated dependencies [a3823b2]
Updated dependencies [43a3efb]
Updated dependencies [524696a]
Updated dependencies [bfa3c3f]
Updated dependencies [5e3301d]
Updated dependencies [dd9f223]
Updated dependencies [46e876c]
Updated dependencies [5f05de2]
Updated dependencies [021ba4c]
Updated dependencies [158aa14]
Updated dependencies [62a2117]
Updated dependencies [d2723e2]
Updated dependencies [fefcd54]
Updated dependencies [beaf2de]
Updated dependencies [369eb6e]
Updated dependencies [06ff734]
Updated dependencies [b659111]
Updated dependencies [5754a23]
Updated dependencies [6c270a6]
Updated dependencies [290e2f0]
Updated dependencies [668dd17]
Updated dependencies [8abf133]
Updated dependencies [e0859b1]
Updated dependencies [04ecd4e]
Updated dependencies [4d5a892]
Updated dependencies [16cebeb]
Updated dependencies [86d30af]
Updated dependencies [8923843]
Updated dependencies [a2795f6]
Updated dependencies [f16b492]
Updated dependencies [4b6fde8]
Updated dependencies [2018df9]
Updated dependencies [fc5a3a2]
Updated dependencies [8ff9210]
- @objectstack/spec@16.0.0
- @objectstack/core@16.0.0

16.0.0-rc.1

Minor Changes

bfa3c3f: Broadcast a transactionalBatch capability bit in discovery so clients negotiate the atomic cross-object batch declaratively, instead of runtime-probing 404/405/501 (#3298).

The atomic cross-object batch endpoint (POST {basePath}/batch, #1604 / ADR-0034 item 4) and its typed SDK surface (client.data.batchTransaction, #3271) already shipped, but discovery never told a client whether a backend actually supports it. Consumers (notably ObjectUI's ObjectStackAdapter) had to probe: fire a /batch, read 404/405 (no route) or 501 (no runtime transaction), and only then fall back to non-atomic client-side simulation. That is "find out by calling", not capability negotiation — it cannot be decided at connect time and cannot serve as the "minimum backend supports /batch" gate that blocks hard-deleting the non-atomic fallback downstream.

WellKnownCapabilitiesSchema gains a required transactionalBatch: boolean, and every discovery producer fills it honestly (declared === enforced), so it never becomes a declared-but-unpopulated bit:
- @objectstack/metadata-protocol (getDiscovery) — reports whether the runtime engine can honour a transaction (typeof engine.transaction === 'function'). The /batch handler runs its ops inside engine.transaction(), which degrades to a non-atomic passthrough (or 501) without one.
- @objectstack/rest (/discovery) — ANDs the engine signal with whether it actually mounts the route (api.enableBatch), so a server with batch disabled reports false even on a transaction-capable engine (never advertise an endpoint that would 404).
- @objectstack/plugin-hono-server (standalone discovery) — reports false: this minimal surface registers CRUD only and does not mount /batch (that ships with @objectstack/rest). Under-reporting is the safe direction — a client keeps its correct-but-slower fallback rather than losing atomicity.
- @objectstack/client — already normalizes hierarchical capabilities to flat booleans, so client.capabilities.transactionalBatch is exposed (and now typed) for declarative consumers.
The bit follows the existing capability semantics: true ⟺ the /batch route is mounted and the runtime can honour a transaction — the exact condition under which the endpoint returns 200 rather than 404/405/501. Additive and behavior-preserving; only the discovery payload gains a field.

Patch Changes

Updated dependencies [6289ec3]
Updated dependencies [8efa395]
Updated dependencies [bfa3c3f]
Updated dependencies [62a2117]
Updated dependencies [06ff734]
- @objectstack/spec@16.0.0-rc.1
- @objectstack/core@16.0.0-rc.1

16.0.0-rc.0

Minor Changes

9ccd1e9: feat(client): typed data.batchTransaction() for the atomic cross-object batch (#1604 / ADR-0034 item 4)

Adds client.data.batchTransaction(operations) (and the environment-scoped client.project(id).data.batchTransaction) — a typed SDK surface for POST {basePath}/batch, the all-or-nothing cross-object transactional batch that master-detail saves go through. Reuses CrossObjectBatchOperation / CrossObjectBatchRequest / CrossObjectBatchResponse from @objectstack/spec/api (also re-exported from the client for convenience); supports { $ref: <opIndex> } intra-batch parent references.

The method is always atomic and deliberately exposes no atomic flag — the endpoint rejects atomic: false with 400 BATCH_NOT_ATOMIC. Non-atomic per-object bulk writes stay on data.batch() / createMany / updateMany, so any best-effort fallback is isolated in the caller's adapter (the ObjectUI masterDetailTx adapter), not in the SDK.
668dd17: Breaking (npm type surface): retire the vestigial feed contracts + protocol surface (ADR-0052 §5 follow-up, #1959).

The service-feed runtime was deleted in #1955; sys_comment / sys_activity are the canonical record-collaboration/timeline backend. This removes the dead type surface that still pointed at the deleted runtime — every removed method was already unreachable (the feed REST route was never mounted → 404; the protocol implementation was never wired with a feed service, so requireFeedService() could only throw). No behavior changes.

No authorable metadata key is removed (the feeds: object capability flag and the RecordActivity UI component config are unchanged), so PROTOCOL_MAJOR stays 15 and this ships as minor rather than a protocol major.

FROM → TO migration for every removed export:
- @objectstack/spec/contracts — IFeedService, CreateFeedItemInput, UpdateFeedItemInput, ListFeedOptions, FeedListResult → removed, no replacement. Comments/activity are plain records: write sys_comment / read sys_activity via the data engine or the REST data API.
- @objectstack/spec/api — FeedApiContracts, FeedApiErrorCode, FeedProtocol, and all feed request/response schemas + types (GetFeed*, CreateFeedItem*, UpdateFeedItem*, DeleteFeedItem*, AddReaction*, RemoveReaction*, PinFeedItem*, UnpinFeedItem*, StarFeedItem*, UnstarFeedItem*, SearchFeed*, GetChangelog*, ChangelogEntry, SubscribeRequest/Response, FeedUnsubscribeRequest, UnsubscribeResponse, FeedPathParams, FeedItemPathParams, FeedListFilterType) → removed. Use the data API against sys_comment / sys_activity (/api/v1/data/sys_comment/…); reactions and threaded replies are fields on sys_comment.
- @objectstack/spec/data — FeedItemSchema/FeedItem, FeedActorSchema/FeedActor, MentionSchema/Mention, ReactionSchema/Reaction, FieldChangeEntrySchema/FieldChangeEntry, FeedVisibility, RecordSubscriptionSchema/RecordSubscription, SubscriptionEventType, and the data-namespace NotificationChannel → removed. FeedItemType and FeedFilterMode are kept (live UI activity-timeline config). For notification channels use NotificationChannelSchema from @objectstack/spec/system.
- @objectstack/client — client.feed.* (list / create / update / delete / addReaction / removeReaction / pin / unpin / star / unstar / search / getChangelog / subscribe / unsubscribe) and the re-exported feed response types → removed. One-line fix: use client.data.* on sys_comment / sys_activity, e.g. client.data.create('sys_comment', { object, record_id, body }) and client.data.find('sys_activity', { filters: [['record_id', '=', id]] }).
- @objectstack/metadata-protocol — ObjectStackProtocolImplementation no longer implements the 14 feed methods; its constructor (engine, getServicesRegistry?, getFeedService?, environmentId?) becomes (engine, getServicesRegistry?, environmentId?). One-line fix: delete the third argument.

Patch Changes

8abf133: Breaking (discovery response shape): retire the residual feed capability surface (#3180, follow-up to #1959 / ADR-0052 §5).

The feed backend was retired long ago; #1959 removed the feed contracts + SDK. This removes the last discovery/dispatcher references to it, and fixes a real bug where the comments capability was permanently false.
- @objectstack/spec — WellKnownCapabilitiesSchema.feed and ApiRoutesSchema.feed (routes.feed) are removed, and the /api/v1/feed entry is dropped from DEFAULT_DISPATCHER_ROUTES. FROM → TO: clients reading discovery.capabilities.feed or discovery.routes.feed → use discovery.capabilities.comments; comments/activity are served by the generic data API on sys_comment / sys_activity (/api/v1/data/sys_comment/…).
- @objectstack/metadata-protocol — getDiscovery() no longer emits the always-false feed service/capability. Bug fix: the comments capability previously keyed off the deleted 'feed' service (so it was permanently false after #1955); it now tracks the presence of the sys_comment object (provided by the always-on audit slate), so declared === enforced.
- @objectstack/client — the internal feed: '/api/v1/feed' route constant is removed (it only existed to satisfy the now-removed ApiRoutes.feed type; no client code used it).
Updated dependencies [f972574]
Updated dependencies [22013aa]
Updated dependencies [3ad3dd5]
Updated dependencies [3a18b60]
Updated dependencies [a8aa34c]
Updated dependencies [e057f42]
Updated dependencies [a3823b2]
Updated dependencies [43a3efb]
Updated dependencies [524696a]
Updated dependencies [5e3301d]
Updated dependencies [dd9f223]
Updated dependencies [46e876c]
Updated dependencies [5f05de2]
Updated dependencies [021ba4c]
Updated dependencies [158aa14]
Updated dependencies [d2723e2]
Updated dependencies [fefcd54]
Updated dependencies [beaf2de]
Updated dependencies [369eb6e]
Updated dependencies [b659111]
Updated dependencies [5754a23]
Updated dependencies [6c270a6]
Updated dependencies [290e2f0]
Updated dependencies [668dd17]
Updated dependencies [8abf133]
Updated dependencies [e0859b1]
Updated dependencies [04ecd4e]
Updated dependencies [4d5a892]
Updated dependencies [16cebeb]
Updated dependencies [86d30af]
Updated dependencies [8923843]
Updated dependencies [a2795f6]
Updated dependencies [f16b492]
Updated dependencies [4b6fde8]
Updated dependencies [2018df9]
Updated dependencies [fc5a3a2]
- @objectstack/spec@16.0.0-rc.0
- @objectstack/core@16.0.0-rc.0

15.1.1

Patch Changes

@objectstack/spec@15.1.1
@objectstack/core@15.1.1

15.1.0

Patch Changes

Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [3fe9df1]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [4109153]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [627f225]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
Updated dependencies [f531a26]
- @objectstack/spec@15.1.0
- @objectstack/core@15.1.0

15.0.0

Patch Changes

Updated dependencies [28b7c28]
Updated dependencies [13749ec]
Updated dependencies [e62c233]
Updated dependencies [ed61c9b]
Updated dependencies [31d04d4]
- @objectstack/spec@15.0.0
- @objectstack/core@15.0.0

14.8.0

Patch Changes

e46169c: 面向最终用户的错误消息去掉调试噪音:REST 数据路由(mapDataError)对沙箱 hook/action 抛错解包 SandboxError.innerMessage(并对丢失实例的情况正则剥离 hook 'x' threw: Error: 包装,保留 TypeError: 等非默认错误名);客户端 SDK 的 error.message 不再拼 [ObjectStack] CODE: 前缀(code 仍在 error.code 上可编程读取)。控制台报错 toast 从 [ObjectStack] hook 'pm_ref_base' threw: Error: 制作基地被… 变为只显示业务消息本身;完整调试包装仍写入服务端日志。
Updated dependencies [16b4bf6]
Updated dependencies [16b4bf6]
Updated dependencies [10e8983]
Updated dependencies [607aaf4]
Updated dependencies [bb71321]
- @objectstack/spec@14.8.0
- @objectstack/core@14.8.0

14.7.0

Patch Changes

Updated dependencies [d6a72eb]
- @objectstack/spec@14.7.0
- @objectstack/core@14.7.0

14.6.0

Patch Changes

e4cf774: fix(auth): single-source Console page-URL construction; correct SMS + OAuth-callback landing paths

Root-cause hardening after the invitation-link fixes. Every user-facing link to a Console page is ${origin}${uiBasePath}${path}, but that composition was hand-written at each call site — which is how the scheme / /_console prefix kept getting dropped one link at a time.

plugin-auth
- New single-source getConsolePageUrl(path) helper; loginPage, consentPage, device verificationUri and the invitation accept URL all compose through it, so future page links can't drift.
- Phone-invite SMS now links to the actual Console sign-in page (${origin}${uiBasePath}/login) via a new {{loginUrl}} template variable instead of the bare origin. {{baseUrl}} is still provided for backward compatibility with tenant-overridden templates.
client
- signInWithProvider now defaults callbackURL to the current page (window.location.href) instead of a hard-coded origin + '/login'. The SDK cannot know the app's mount path (Console lives under /_console), so returning the user to where they started is the only base-path-correct default; it also mirrors linkSocial. Pass an explicit callbackURL to override.
Updated dependencies [609cb13]
Updated dependencies [ce6d151]
- @objectstack/spec@14.6.0
- @objectstack/core@14.6.0

14.5.0

Patch Changes

Updated dependencies [526805e]
Updated dependencies [d79ca07]
Updated dependencies [33ebd34]
Updated dependencies [c044f08]
Updated dependencies [01274eb]
- @objectstack/spec@14.5.0
- @objectstack/core@14.5.0

14.4.0

Patch Changes

Updated dependencies [7953832]
Updated dependencies [82e745e]
Updated dependencies [f3035bd]
Updated dependencies [82c0d94]
Updated dependencies [7449476]
- @objectstack/spec@14.4.0
- @objectstack/core@14.4.0

14.3.0

Patch Changes

Updated dependencies [2a71f48]
Updated dependencies [02f6af4]
Updated dependencies [c1064f1]
- @objectstack/spec@14.3.0
- @objectstack/core@14.3.0

14.2.0

Patch Changes

Updated dependencies [ac8f029]
Updated dependencies [4ab9958]
- @objectstack/spec@14.2.0
- @objectstack/core@14.2.0

14.1.0

Patch Changes

Updated dependencies [5a8465f]
Updated dependencies [7f8620b]
Updated dependencies [82ba3a6]
- @objectstack/spec@14.1.0
- @objectstack/core@14.1.0

14.0.0

Patch Changes

Updated dependencies [0a8e685]
Updated dependencies [afa8115]
Updated dependencies [80f12ca]
Updated dependencies [e2fa074]
Updated dependencies [23c8668]
Updated dependencies [29f017d]
Updated dependencies [216fa9a]
Updated dependencies [6c22b12]
- @objectstack/spec@14.0.0
- @objectstack/core@14.0.0

13.0.0

Patch Changes

Updated dependencies [6d83431]
Updated dependencies [01917c2]
Updated dependencies [b271691]
Updated dependencies [a5a1e41]
Updated dependencies [466adf6]
Updated dependencies [5be00c3]
Updated dependencies [466adf6]
Updated dependencies [2bee609]
Updated dependencies [fc7e7f7]
- @objectstack/spec@13.0.0
- @objectstack/core@13.0.0

12.6.0

Patch Changes

Updated dependencies [6cebf22]
Updated dependencies [21420d9]
- @objectstack/spec@12.6.0
- @objectstack/core@12.6.0

12.5.0

Patch Changes

Updated dependencies [8b3d363]
- @objectstack/spec@12.5.0
- @objectstack/core@12.5.0

12.4.0

Patch Changes

Updated dependencies [60dc3ba]
- @objectstack/spec@12.4.0
- @objectstack/core@12.4.0

12.3.0

Patch Changes

Updated dependencies [e7eceec]
- @objectstack/spec@12.3.0
- @objectstack/core@12.3.0

12.2.0

Patch Changes

Updated dependencies [fce8ff4]
Updated dependencies [3962023]
Updated dependencies [2bb193d]
Updated dependencies [0426d27]
Updated dependencies [da807f7]
Updated dependencies [4f5b791]
- @objectstack/spec@12.2.0
- @objectstack/core@12.2.0

12.1.0

Patch Changes

Updated dependencies [93e6d02]
- @objectstack/spec@12.1.0
- @objectstack/core@12.1.0

12.0.0

Patch Changes

Updated dependencies [a8df396]
Updated dependencies [e695fe0]
Updated dependencies [7c09621]
Updated dependencies [7709db4]
Updated dependencies [2082109]
Updated dependencies [7c09621]
Updated dependencies [9860de4]
Updated dependencies [069c205]
- @objectstack/spec@12.0.0
- @objectstack/core@12.0.0

11.10.0

Patch Changes

Updated dependencies [6a9397e]
Updated dependencies [c0efe5d]
- @objectstack/spec@11.10.0
- @objectstack/core@11.10.0

11.9.0

Patch Changes

Updated dependencies [d3595d9]
- @objectstack/spec@11.9.0
- @objectstack/core@11.9.0

11.8.0

Patch Changes

@objectstack/spec@11.8.0
@objectstack/core@11.8.0

11.7.0

Patch Changes

Updated dependencies [5178906]
- @objectstack/spec@11.7.0
- @objectstack/core@11.7.0

11.6.0

Patch Changes

@objectstack/spec@11.6.0
@objectstack/core@11.6.0

11.5.0

Patch Changes

Updated dependencies [6ee4f04]
Updated dependencies [c1e3a65]
- @objectstack/spec@11.5.0
- @objectstack/core@11.5.0

11.4.0

Patch Changes

Updated dependencies [5821c51]
Updated dependencies [a0fce3f]
- @objectstack/spec@11.4.0
- @objectstack/core@11.4.0

11.3.0

Patch Changes

Updated dependencies [58e8e31]
Updated dependencies [b4a5df0]
- @objectstack/spec@11.3.0
- @objectstack/core@11.3.0

11.2.0

Patch Changes

Updated dependencies [d0f4b13]
Updated dependencies [302bdab]
- @objectstack/spec@11.2.0
- @objectstack/core@11.2.0

11.1.0

Minor Changes

7087cfe: Remove the unused HTTP framework adapters and the MSW plugin — the open edition ships the Hono adapter only.

The express / fastify / nextjs / nestjs / nuxt / sveltekit adapters and @objectstack/plugin-msw had zero internal consumers and were not dogfooded — pure release/maintenance surface (and an untested-integration liability). They are removed; @objectstack/hono (the adapter actually used, via @objectstack/client) is kept.
- Deleted packages: @objectstack/express, @objectstack/fastify, @objectstack/nextjs, @objectstack/nestjs, @objectstack/nuxt, @objectstack/sveltekit, @objectstack/plugin-msw (fixed group 73 → 66).
- @objectstack/client: dropped the plugin-msw / msw dev usage (MSW test removed).
- HttpDispatcher (the dispatch engine) is now used only by the Hono adapter + the internal dispatcher-plugin, so its misleading @deprecated → createDispatcherPlugin note (createDispatcherPlugin is a kernel plugin, not a drop-in) is corrected.
Anyone needing another framework adapter can build one on the public HttpDispatcher / createDispatcherPlugin API or maintain it out-of-tree.

Patch Changes

Updated dependencies [ce0b4f6]
Updated dependencies [9ccfcd6]
Updated dependencies [ecf193f]
Updated dependencies [51bec81]
Updated dependencies [3e593a7]
Updated dependencies [63d5403]
- @objectstack/core@11.1.0
- @objectstack/spec@11.1.0

11.0.0

Patch Changes

1b00ba2: chore(client): remove dead projects.* env-member SDK methods (cloud#533 / ADR-0024 D9)

Removes projects.listMembers / addMember / updateMemberRole / removeMember, which called GET/POST/PATCH/DELETE /api/v1/cloud/environments/:id/members. Those control-plane endpoints were deleted in cloud#533 (retiring sys_environment_member), so the methods returned 404. Org membership/invites now flow through the better-auth organization plugin (organization.inviteMember / listMembers / …); objectui already uses organization.* and no in-repo callers remained.

The membership field on the projects.get() response is unchanged — cloud#533 still returns it on the single-env GET (re-sourced to the caller's org sys_member role).
Updated dependencies [ab5718a]
Updated dependencies [4845c12]
Updated dependencies [c1a754a]
Updated dependencies [6fbe91f]
Updated dependencies [715d667]
Updated dependencies [5eef4cf]
Updated dependencies [72759e1]
Updated dependencies [6c4fbd9]
Updated dependencies [ef3ed67]
Updated dependencies [cd51229]
Updated dependencies [7697a0e]
Updated dependencies [e7e04f1]
Updated dependencies [cfd5ac4]
Updated dependencies [2be5c1f]
Updated dependencies [ad143ce]
Updated dependencies [5c4a8c8]
Updated dependencies [3afaeed]
Updated dependencies [8801c02]
Updated dependencies [3d04e06]
Updated dependencies [4a84c98]
Updated dependencies [c715d25]
Updated dependencies [aa33b02]
Updated dependencies [d980f0d]
Updated dependencies [a658523]
Updated dependencies [82ff91c]
Updated dependencies [638f472]
- @objectstack/spec@11.0.0
- @objectstack/core@11.0.0

10.3.0

Patch Changes

@objectstack/spec@10.3.0
@objectstack/core@10.3.0

10.2.0

Patch Changes

Updated dependencies [b496498]
- @objectstack/spec@10.2.0
- @objectstack/core@10.2.0

10.1.0

Patch Changes

Updated dependencies [49da36e]
Updated dependencies [ac79f16]
- @objectstack/spec@10.1.0
- @objectstack/core@10.1.0

10.0.0

Patch Changes

Updated dependencies [d7ff626]
Updated dependencies [2a1b16b]
Updated dependencies [e16f2a8]
Updated dependencies [e411a82]
Updated dependencies [a581385]
Updated dependencies [d5f6d29]
Updated dependencies [220ce5b]
Updated dependencies [3efe334]
Updated dependencies [feead7e]
Updated dependencies [6ca20b3]
Updated dependencies [5f875fe]
Updated dependencies [b469950]
- @objectstack/spec@10.0.0
- @objectstack/core@10.0.0

9.11.0

Patch Changes

Updated dependencies [e7f6539]
Updated dependencies [2365d07]
Updated dependencies [6595b53]
Updated dependencies [fa8964d]
Updated dependencies [36138c7]
Updated dependencies [a8e4f3b]
Updated dependencies [4c213c2]
Updated dependencies [2afb612]
- @objectstack/spec@9.11.0
- @objectstack/core@9.11.0

9.10.0

Patch Changes

Updated dependencies [db02bd5]
Updated dependencies [641675d]
Updated dependencies [94e9040]
Updated dependencies [1f88fd9]
Updated dependencies [1f88fd9]
- @objectstack/spec@9.10.0
- @objectstack/core@9.10.0

9.9.1

Patch Changes

@objectstack/spec@9.9.1
@objectstack/core@9.9.1

9.9.0

Patch Changes

Updated dependencies [84249a4]
Updated dependencies [11af299]
Updated dependencies [d5774b5]
Updated dependencies [134043a]
Updated dependencies [90108e0]
Updated dependencies [9afeb2d]
Updated dependencies [6bec07e]
Updated dependencies [601cc11]
Updated dependencies [575448d]
- @objectstack/spec@9.9.0
- @objectstack/core@9.9.0

9.8.0

Patch Changes

Updated dependencies [97c55b3]
Updated dependencies [1b1f490]
- @objectstack/spec@9.8.0
- @objectstack/core@9.8.0

9.7.0

Patch Changes

@objectstack/spec@9.7.0
@objectstack/core@9.7.0

9.6.0

Patch Changes

Updated dependencies [d1e930a]
Updated dependencies [71578f2]
Updated dependencies [5e3a301]
Updated dependencies [5db2742]
- @objectstack/spec@9.6.0
- @objectstack/core@9.6.0

9.5.1

Patch Changes

Updated dependencies [ee72aae]
- @objectstack/spec@9.5.1
- @objectstack/core@9.5.1

9.5.0

Patch Changes

Updated dependencies [d08551c]
Updated dependencies [707aeed]
Updated dependencies [7a103d4]
Updated dependencies [4b01250]
- @objectstack/spec@9.5.0
- @objectstack/core@9.5.0

9.4.0

Patch Changes

Updated dependencies [060467a]
Updated dependencies [0856476]
Updated dependencies [b678d8c]
Updated dependencies [b678d8c]
Updated dependencies [b678d8c]
- @objectstack/spec@9.4.0
- @objectstack/core@9.4.0

9.3.0

Patch Changes

Updated dependencies [1ada658]
Updated dependencies [3219191]
Updated dependencies [290f631]
Updated dependencies [50b7b47]
Updated dependencies [f15d6f6]
Updated dependencies [f8684ea]
Updated dependencies [b4765be]
- @objectstack/spec@9.3.0
- @objectstack/core@9.3.0

9.2.0

Patch Changes

Updated dependencies [2f57b75]
Updated dependencies [2f57b75]
- @objectstack/spec@9.2.0
- @objectstack/core@9.2.0

9.1.0

Patch Changes

Updated dependencies [b9062c9]
- @objectstack/spec@9.1.0
- @objectstack/core@9.1.0

9.0.1

Patch Changes

Updated dependencies [1817845]
- @objectstack/spec@9.0.1
- @objectstack/core@9.0.1

9.0.0

Patch Changes

Updated dependencies [4c3f693]
Updated dependencies [0bf39f1]
Updated dependencies [f533f42]
Updated dependencies [1c83ee8]
- @objectstack/spec@9.0.0
- @objectstack/core@9.0.0

8.0.1

Patch Changes

@objectstack/spec@8.0.1
@objectstack/core@8.0.1

8.0.0

Patch Changes

Updated dependencies [a46c017]
Updated dependencies [b990b89]
Updated dependencies [99111ec]
Updated dependencies [d5a8161]
Updated dependencies [5cf1f1b]
Updated dependencies [9ef89d4]
Updated dependencies [3306d2f]
Updated dependencies [c262301]
Updated dependencies [bc44195]
Updated dependencies [9e2e229]
- @objectstack/spec@8.0.0
- @objectstack/core@8.0.0

7.9.0

Patch Changes

@objectstack/spec@7.9.0
@objectstack/core@7.9.0

7.8.0

Patch Changes

Updated dependencies [06f2bbb]
Updated dependencies [36719db]
Updated dependencies [424ab26]
- @objectstack/spec@7.8.0
- @objectstack/core@7.8.0

7.7.0

Patch Changes

Updated dependencies [b391955]
Updated dependencies [f06b64e]
Updated dependencies [023bf93]
- @objectstack/spec@7.7.0
- @objectstack/core@7.7.0

7.6.0

Minor Changes

2170ad9: client SDK: add approvals namespace; remove dead workflow approve/reject surface (ADR-0019)

ADR-0019 collapsed approval into Flow: approval is no longer a workflow step but a first-class flow node that opens a request and suspends the run, with a human decision resuming the flow down the matching approve / reject edge. The server already exposes this as a dedicated /api/v1/approvals surface (registerApprovalsEndpoints), but the client SDK still carried the old approval-on-workflow methods, which pointed at routes that never existed.
- @objectstack/client gains a client.approvals namespace backed by the real REST surface:
  - listRequests(filter?) → GET /approvals/requests (the "my approvals" inbox; filter by status (single or array), object, recordId, approverId, submitterId).
  - getRequest(id) → GET /approvals/requests/:id.
  - approve(id, { actorId?, comment? }) / reject(id, …) → POST /approvals/requests/:id/{approve,reject} (records a decision and resumes the owning flow run).
  - listActions(id) → GET /approvals/requests/:id/actions (audit trail).
  The approval runtime types (ApprovalRequestRow, ApprovalActionRow, ApprovalStatus, ApprovalDecisionInput, ApprovalDecisionResult) are re-exported so consumers can type the namespace without reaching into @objectstack/spec.
- Removed the dead workflow approve/reject surface. client.workflow.approve / client.workflow.reject and the backing WorkflowApprove* / WorkflowReject* protocol schemas, types, IProtocolService methods, and the /approve / /reject entries in DEFAULT_WORKFLOW_ROUTES are gone — approval decisions are no longer recorded on a workflow record. workflow is reclaimed for state machines, so getConfig / getState / transition are unchanged.
- Discovery advertises the new route key: ApiRoutesSchema.approvals.

Patch Changes

Updated dependencies [955d4c8]
Updated dependencies [c4a4cbd]
Updated dependencies [b046ec2]
Updated dependencies [2170ad9]
Updated dependencies [02d6359]
Updated dependencies [7648242]
Updated dependencies [8fa1e7f]
Updated dependencies [55866f5]
Updated dependencies [60f9c45]
- @objectstack/spec@7.6.0
- @objectstack/core@7.6.0

7.5.0

Patch Changes

@objectstack/spec@7.5.0
@objectstack/core@7.5.0

7.4.1

Patch Changes

@objectstack/spec@7.4.1
@objectstack/core@7.4.1

7.4.0

Minor Changes

58b450b: Make metadata labels follow the active UI language without a page refresh (#1319).

The client now carries the active locale on every request (Accept-Language, setLocale/getLocale), the protocol ETag is locale-aware so cached metadata no longer collides across languages, and the client-react metadata hooks refetch when the locale changes. The apps/account console wires its router locale through so a language switch relabels server-resolved object/field/view labels in place instead of leaving the UI half-translated until reload.

Patch Changes

Updated dependencies [23c7107]
Updated dependencies [c72daad]
Updated dependencies [f115182]
Updated dependencies [2faf9f2]
Updated dependencies [2faf9f2]
Updated dependencies [2faf9f2]
Updated dependencies [58b450b]
Updated dependencies [82eb6cf]
Updated dependencies [13d8653]
Updated dependencies [ff3d006]
Updated dependencies [5e831de]
- @objectstack/spec@7.4.0
- @objectstack/core@7.4.0

7.3.0

Patch Changes

Updated dependencies [5e7c554]
- @objectstack/spec@7.3.0
- @objectstack/core@7.3.0

7.2.1

Patch Changes

@objectstack/spec@7.2.1
@objectstack/core@7.2.1

7.2.0

Patch Changes

@objectstack/spec@7.2.0
@objectstack/core@7.2.0

7.1.0

Patch Changes

Updated dependencies [47a92f4]
- @objectstack/spec@7.1.0
- @objectstack/core@7.1.0

7.0.0

Patch Changes

Updated dependencies [74470ad]
Updated dependencies [d29617e]
Updated dependencies [dc72172]
- @objectstack/spec@7.0.0
- @objectstack/core@7.0.0

6.9.0

Patch Changes

@objectstack/spec@6.9.0
@objectstack/core@6.9.0

6.8.1

Patch Changes

@objectstack/spec@6.8.1
@objectstack/core@6.8.1

6.8.0

Patch Changes

Updated dependencies [6e88f77]
Updated dependencies [c8b9f57]
- @objectstack/spec@6.8.0
- @objectstack/core@6.8.0

6.7.1

Patch Changes

@objectstack/spec@6.7.1
@objectstack/core@6.7.1

6.7.0

Patch Changes

Updated dependencies [430067b]
Updated dependencies [4f9e9d4]
- @objectstack/spec@6.7.0
- @objectstack/core@6.7.0

6.6.0

Patch Changes

Updated dependencies [a49cfc2]
- @objectstack/spec@6.6.0
- @objectstack/core@6.6.0

6.5.1

Patch Changes

@objectstack/spec@6.5.1
@objectstack/core@6.5.1

6.5.0

Patch Changes

@objectstack/spec@6.5.0
@objectstack/core@6.5.0

6.4.0

Patch Changes

Updated dependencies [f8651cc]
Updated dependencies [f8651cc]
Updated dependencies [0bf6f9a]
- @objectstack/spec@6.4.0
- @objectstack/core@6.4.0

6.3.0

Patch Changes

@objectstack/spec@6.3.0
@objectstack/core@6.3.0

6.2.0

Patch Changes

Updated dependencies [b4c74a9]
- @objectstack/spec@6.2.0
- @objectstack/core@6.2.0

6.1.1

Patch Changes

@objectstack/spec@6.1.1
@objectstack/core@6.1.1

6.1.0

Patch Changes

Updated dependencies [93c0589]
- @objectstack/spec@6.1.0
- @objectstack/core@6.1.0

6.0.0

Major Changes

944f187: # v5.0 — project → environment hard rename

The runtime concept previously called "project" (per-tenant business workspace; Org → Project → Branch hierarchy; per-project ObjectKernel, per-project DB, per-project artifact) is now uniformly called "environment".

This is a hard rename with no aliases, deprecation shims, or compatibility layer. Upgrade requires a coordinated update of CLI, runtime, server, and any clients calling the REST API.

Note: "project" in the npm / monorepo sense (the framework itself, package.json, tsconfig project references, vitest projects config) is unchanged.

Breaking changes

CLI
- Flags renamed:
  - --project / -p → --environment / -e (os publish, os rollback)
  - --project-id → --environment-id (os dev)
- Default local env id: proj_local → env_local.
- Env var: OS_PROJECT_ID → OS_ENVIRONMENT_ID.
- Command group renamed: os projects ... → os environments ... (bind, create, list, show, switch).
- Persisted auth-config key: activeProjectId → activeEnvironmentId.
HTTP / REST
- Scoped routes: /api/v1/projects/:projectId/... → /api/v1/environments/:environmentId/....
- Cloud control-plane routes: /api/v1/cloud/projects/... → /api/v1/cloud/environments/... (including /cloud/environments/:id/artifact, /cloud/environments/:id/metadata, /cloud/environments/:id/credentials/rotate, etc.).
- Header: X-Project-Id (and lowercase x-project-id) → X-Environment-Id (x-environment-id).
- Route param name in handlers: req.params.projectId → req.params.environmentId.
- Hostname-routing and tenant-resolution code-paths use environmentId end-to-end.
Runtime / spec
- Exported symbols (no aliases):
  - createSystemProjectPlugin → createSystemEnvironmentPlugin
  - SYSTEM_PROJECT_ID → SYSTEM_ENVIRONMENT_ID
  - ProjectArtifactSchema → EnvironmentArtifactSchema
  - PROJECT_ARTIFACT_SCHEMA_VERSION → ENVIRONMENT_ARTIFACT_SCHEMA_VERSION
  - ObjectOSProjectPlugin → ObjectOSEnvironmentPlugin
  - createSingleProjectPlugin → createSingleEnvironmentPlugin
- Plugin identifier strings:
  - com.objectstack.runtime.objectos-project → objectos-environment
  - com.objectstack.studio.single-project → single-environment
  - com.objectstack.multi-project → multi-environment
  - com.objectstack.runtime.system-project → system-environment
- Provisioning hook: provisionSystemProject → provisionSystemEnvironment.
Database / schemas
- Column renames on sys_metadata and sys_metadata_history: project_id → environment_id.
- Column renames on sys_activity: project_id → environment_id (plus index).
- Object renames in platform-objects metadata: sys_project → sys_environment (lookup targets), sys_project_member → sys_environment_member, sys_project_credential → sys_environment_credential.
- Auth-context field: active_project_id → active_environment_id.
- JSON schemas under packages/spec/json-schema/system/: ProjectArtifact*.json → EnvironmentArtifact*.json (regenerated at build).
Automatic forward migration

A new migration migrateProjectIdToEnvironmentId (packages/metadata/src/migrations/migrate-project-id-to-environment-id.ts) auto-runs from DatabaseLoader.ensureSchema() on bootstrap and rewrites any existing project_id column on sys_metadata / sys_metadata_history to environment_id (idempotent, best-effort). Existing rows are preserved.

The legacy reverse migration migrateEnvIdToProjectId is retained verbatim for historical / disaster-recovery use; it is not auto-run.

Migration guide
```
-os publish --project proj_xyz
+os publish --environment env_xyz

-curl -H "X-Project-Id: env_xyz" https://api.example.com/api/v1/data/customer
+curl -H "X-Environment-Id: env_xyz" https://api.example.com/api/v1/data/customer

-OS_PROJECT_ID=env_xyz os dev
+OS_ENVIRONMENT_ID=env_xyz os dev

-import { createSystemProjectPlugin, SYSTEM_PROJECT_ID } from "@objectstack/runtime";
+import { createSystemEnvironmentPlugin, SYSTEM_ENVIRONMENT_ID } from "@objectstack/runtime";

-import { ProjectArtifactSchema } from "@objectstack/spec";
+import { EnvironmentArtifactSchema } from "@objectstack/spec";
```
If you maintain a Cloud control-plane deployment, the cloud repository must be updated in lockstep to pick up the new plugin identifier strings (single-environment, multi-environment, objectos-environment).

Patch Changes

Updated dependencies [629a716]
Updated dependencies [dbc4f7d]
Updated dependencies [944f187]
- @objectstack/spec@6.0.0
- @objectstack/core@6.0.0

5.2.0

Patch Changes

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

5.1.0

Patch Changes

Updated dependencies [75f4ee6]
Updated dependencies [823d559]
- @objectstack/spec@5.1.0
- @objectstack/core@5.1.0

5.0.0

Patch Changes

Updated dependencies [2f9073a]
- @objectstack/spec@5.0.0
- @objectstack/core@5.0.0

4.2.0

Minor Changes

2869891: feat: Optimistic Concurrency Control (OCC) via If-Match

Update and Delete requests now accept an optional version token. When supplied, the protocol compares it against the record's current updated_at (or version column when available) and rejects with 409 CONCURRENT_UPDATE on mismatch, preventing silent overwrites when two clients edit the same record.

Wire formats (opt-in, all server- and client-backward-compatible):
- PATCH /data/{object}/{id} — supports If-Match: "<token>" header or expectedVersion: "<token>" body field (body wins when both present).
- DELETE /data/{object}/{id} — supports If-Match header or ?expectedVersion=... query param.
- Conflict response: 409 { error, code: 'CONCURRENT_UPDATE', currentVersion, currentRecord } so the client can offer Reload / Overwrite / Cancel UX.
Behaviour
- Missing/empty version → no check (legacy callers unaffected).
- Record not found during the version probe → no check; the downstream write produces a normal 404.
- Object has no updated_at column → no check (explicit opt-out for objects without timestamps).
- Quoted RFC-7232 tokens ("…") are accepted and unquoted before comparison.
Client

client.data.update(resource, id, data, { ifMatch }) and client.data.delete(resource, id, { ifMatch }) now forward the token as an If-Match header.

Application-level CAS (findOne + compare in protocol.ts) is used in this slice to avoid touching every storage driver. A small TOCTOU window remains; for the B2B record-editing latencies this protects against, it is more than sufficient. Drivers may later be upgraded to atomic WHERE id=? AND updated_at=? writes for true CAS without changing the public API.

Tests: 7 new cases in protocol-data.test.ts cover opt-in, match, mismatch, quote-stripping, no-timestamps, empty-token, and the delete path.

Patch Changes

Updated dependencies [2869891]
- @objectstack/spec@4.2.0
- @objectstack/core@4.2.0

4.1.1

Patch Changes

5326c6b: Studio developer UX overhaul.
- Inspector drawer (right Sheet, toggle via header button or ]) with API / Source / Refs tabs that auto-populate from the current resource detail page.
- Problems panel (status bar pill + [) that subscribes to object/view/flow/hook changes and surfaces unknown object refs, missing field refs, and broken triggers with deep-links back to source.
- Keyboard shortcuts: g o|f|v|a|s|p navigation, [ problems, ] inspector, ? help dialog.
- Resource actions menu (⋯ on detail page header): Copy as curl / fetch() / defineX() TypeScript / Metadata JSON; Open in VS Code; Open API endpoint.
- Welcome onboarding empty-state in the developer overview when a package has no metadata.
- New StudioShell wrapper; TopBar gains a rightSlot prop for Inspector / Help buttons.
@objectstack/client: surface plain-string error bodies (e.g. RECORD_LOCKED: …) in fetch error messages instead of swallowing them as Bad Request.
- @objectstack/spec@4.1.1
- @objectstack/core@4.1.1

4.1.0

Patch Changes

Updated dependencies [2108c30]
Updated dependencies [23db640]
- @objectstack/spec@4.1.0
- @objectstack/core@4.1.0

4.0.5

Patch Changes

15e0df6: chore: unify all package versions to a single patch release
Updated dependencies [15e0df6]
- @objectstack/spec@4.0.5
- @objectstack/core@4.0.5

4.0.4

Patch Changes

Updated dependencies [326b66b]
- @objectstack/spec@4.0.4
- @objectstack/core@4.0.4

4.0.3

Patch Changes

@objectstack/spec@4.0.3
@objectstack/core@4.0.3

4.0.2

Patch Changes

5f659e9: fix ai
Updated dependencies [5f659e9]
- @objectstack/spec@4.0.2
- @objectstack/core@4.0.2

4.0.0

Minor Changes

f08ffc3: Fix discovery API endpoint routing and protocol consistency.

Discovery route standardization:
- All adapters (Express, Fastify, Hono, NestJS, Next.js, Nuxt, SvelteKit) now mount the discovery endpoint at {prefix}/discovery instead of {prefix} root.
- .well-known/objectstack redirects now point to {prefix}/discovery.
- Client connect() fallback URL changed from /api/v1 to /api/v1/discovery.
- Runtime dispatcher handles both /discovery (standard) and / (legacy) for backward compatibility.
Schema & route alignment:
- Added storage (service: file-storage) and feed (service: data) routes to DEFAULT_DISPATCHER_ROUTES.
- Added feed and discovery fields to ApiRoutesSchema.
- Unified GetDiscoveryResponseSchema with DiscoverySchema as single source of truth.
- Client getRoute('feed') fallback updated from /api/v1/data to /api/v1/feed.
Type safety:
- Extracted ApiRouteType from ApiRoutes keys for type-safe client route resolution.
- Removed as any type casting in client route access.
e0b0a78: Deprecate DataEngineQueryOptions in favor of QueryAST-aligned EngineQueryOptions.

Engine, Protocol, and Client now use standard QueryAST parameter names:
- filter → where
- select → fields
- sort → orderBy
- skip → offset
- populate → expand
- top → limit
The old DataEngine* schemas and types are preserved with @deprecated markers for backward compatibility.

Patch Changes

Updated dependencies [f08ffc3]
Updated dependencies [e0b0a78]
- @objectstack/spec@4.0.0
- @objectstack/core@4.0.0

3.3.1

Patch Changes

@objectstack/spec@3.3.1
@objectstack/core@3.3.1

3.3.0

Patch Changes

@objectstack/spec@3.3.0
@objectstack/core@3.3.0

3.2.9

Patch Changes

@objectstack/spec@3.2.9
@objectstack/core@3.2.9

3.2.8

Patch Changes

@objectstack/spec@3.2.8
@objectstack/core@3.2.8

3.2.7

Patch Changes

@objectstack/spec@3.2.7
@objectstack/core@3.2.7

3.2.6

Patch Changes

@objectstack/spec@3.2.6
@objectstack/core@3.2.6

3.2.5

Patch Changes

@objectstack/spec@3.2.5
@objectstack/core@3.2.5

3.2.4

Patch Changes

@objectstack/spec@3.2.4
@objectstack/core@3.2.4

3.2.3

Patch Changes

@objectstack/spec@3.2.3
@objectstack/core@3.2.3

3.2.2

Patch Changes

Updated dependencies [46defbb]
- @objectstack/spec@3.2.2
- @objectstack/core@3.2.2

3.2.1

Patch Changes

Updated dependencies [850b546]
- @objectstack/spec@3.2.1
- @objectstack/core@3.2.1

3.2.0

Patch Changes

Updated dependencies [5901c29]
- @objectstack/spec@3.2.0
- @objectstack/core@3.2.0

3.1.1

Patch Changes

Updated dependencies [953d667]
- @objectstack/spec@3.1.1
- @objectstack/core@3.1.1

3.1.0

Patch Changes

Updated dependencies [0088830]
- @objectstack/spec@3.1.0
- @objectstack/core@3.1.0

3.0.11

Patch Changes

Updated dependencies [92d9d99]
- @objectstack/spec@3.0.11
- @objectstack/core@3.0.11

3.0.10

Patch Changes

Updated dependencies [d1e5d31]
- @objectstack/spec@3.0.10
- @objectstack/core@3.0.10

3.0.9

Patch Changes

Updated dependencies [15e0df6]
- @objectstack/spec@3.0.9
- @objectstack/core@3.0.9

3.0.8

Patch Changes

Updated dependencies [5a968a2]
- @objectstack/spec@3.0.8
- @objectstack/core@3.0.8

3.0.7

Patch Changes

Updated dependencies [0119bd7]
Updated dependencies [5426bdf]
- @objectstack/spec@3.0.7
- @objectstack/core@3.0.7

3.0.6

Patch Changes

Updated dependencies [5df254c]
- @objectstack/spec@3.0.6
- @objectstack/core@3.0.6

3.0.5

Patch Changes

Updated dependencies [23a4a68]
- @objectstack/spec@3.0.5
- @objectstack/core@3.0.5

3.0.4

Patch Changes

Updated dependencies [d738987]
- @objectstack/spec@3.0.4
- @objectstack/core@3.0.4

3.0.3

Patch Changes

c7267f6: Patch release for maintenance updates and improvements.
Updated dependencies [c7267f6]
- @objectstack/spec@3.0.3
- @objectstack/core@3.0.3

3.0.2

Patch Changes

Updated dependencies [28985f5]
- @objectstack/spec@3.0.2
- @objectstack/core@3.0.2

3.0.1

Patch Changes

Updated dependencies [389725a]
- @objectstack/spec@3.0.1
- @objectstack/core@3.0.1

3.0.0

Major Changes

Release v3.0.0 — unified version bump for all ObjectStack packages.

Patch Changes

Updated dependencies
- @objectstack/spec@3.0.0
- @objectstack/core@3.0.0

2.0.7

Patch Changes

Updated dependencies
- @objectstack/spec@2.0.7
- @objectstack/core@2.0.7

2.0.6

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@2.0.6
- @objectstack/core@2.0.6

2.0.5

Patch Changes

Updated dependencies
- @objectstack/spec@2.0.5
- @objectstack/core@2.0.5

2.0.4

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@2.0.4
- @objectstack/core@2.0.4

2.0.3

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@2.0.3
- @objectstack/core@2.0.3

2.0.2

Patch Changes

Updated dependencies [1db8559]
- @objectstack/spec@2.0.2
- @objectstack/core@2.0.2

2.0.1

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@2.0.1
- @objectstack/core@2.0.1

2.0.0

Patch Changes

Updated dependencies [38e5dd5]
Updated dependencies [38e5dd5]
- @objectstack/spec@2.0.0
- @objectstack/core@2.0.0

1.0.12

Patch Changes

chore: add Vercel deployment configs, simplify console runtime configuration
Updated dependencies
- @objectstack/spec@1.0.12
- @objectstack/core@1.0.12

1.0.11

Patch Changes

@objectstack/spec@1.0.11
@objectstack/core@1.0.11

1.0.10

Patch Changes

Updated dependencies [10f52e1]
- @objectstack/core@1.0.10
- @objectstack/spec@1.0.10

1.0.9

Patch Changes

@objectstack/spec@1.0.9
@objectstack/core@1.0.9

1.0.8

Patch Changes

@objectstack/spec@1.0.8
@objectstack/core@1.0.8

1.0.7

Patch Changes

ebdf787: feat: implement standard service discovery via /.well-known/objectstack
- @objectstack/spec@1.0.7
- @objectstack/core@1.0.7

1.0.6

Patch Changes

Updated dependencies [a7f7b9d]
- @objectstack/spec@1.0.6
- @objectstack/core@1.0.6

1.0.5

Patch Changes

b1d24bd: refactor: migrate build system from tsc to tsup for faster builds
- Replaced tsc with tsup (using esbuild) across all packages
- Added shared tsup.config.ts in workspace root
- Added tsup as workspace dev dependency
- significantly improved build performance
Updated dependencies [b1d24bd]
- @objectstack/core@1.0.5
- @objectstack/spec@1.0.5

1.0.4

Patch Changes

@objectstack/spec@1.0.4
@objectstack/core@1.0.4

1.0.3

Patch Changes

Updated dependencies [fb2eabd]
- @objectstack/core@1.0.3
- @objectstack/spec@1.0.3

1.0.2

Patch Changes

a0a6c85: Infrastructure and development tooling improvements
- Add changeset configuration for automated version management
- Add comprehensive GitHub Actions workflows (CI, CodeQL, linting, releases)
- Add development configuration files (.cursorrules, .github/prompts)
- Add documentation files (ARCHITECTURE.md, CONTRIBUTING.md, workflows docs)
- Update test script configuration in package.json
- Add @objectstack/cli to devDependencies for better development experience
109fc5b: Unified patch release to align all package versions.
Updated dependencies [a0a6c85]
Updated dependencies [109fc5b]
- @objectstack/spec@1.0.2
- @objectstack/core@1.0.2

1.0.1

Patch Changes

@objectstack/spec@1.0.1
@objectstack/core@1.0.1

1.0.0

Major Changes

Major version release for ObjectStack Protocol v1.0.
- Stabilized Protocol Definitions
- Enhanced Runtime Plugin Support
- Fixed Type Compliance across Monorepo

Patch Changes

Updated dependencies
- @objectstack/spec@1.0.0
- @objectstack/core@1.0.0

0.9.2

Patch Changes

Updated dependencies
- @objectstack/spec@0.9.2
- @objectstack/core@0.9.2

0.9.1

Patch Changes

Patch release for maintenance and stability improvements. All packages updated with unified versioning.
Updated dependencies
- @objectstack/spec@0.9.1
- @objectstack/core@0.9.1

0.8.2

Patch Changes

Updated dependencies [555e6a7]
- @objectstack/spec@0.8.2
- @objectstack/core@0.8.2

0.8.1

Patch Changes

@objectstack/spec@0.8.1
@objectstack/core@0.8.1

1.0.0

Minor Changes

Upgrade to Zod v4 and Protocol Improvements

This release includes a major upgrade to the core validation engine (Zod v4) and aligns all protocol definitions with stricter type safety.

Patch Changes

Updated dependencies
- @objectstack/spec@1.0.0
- @objectstack/core@1.0.0

0.7.2

Patch Changes

fb41cc0: Patch release: Updated documentation and JSON schemas
Updated dependencies [fb41cc0]
- @objectstack/spec@0.7.2
- @objectstack/core@0.7.2

0.7.1

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@0.7.1
- @objectstack/core@0.7.1

0.6.1

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@0.6.1

0.6.0

Minor Changes

b2df5f7: Unified version bump to 0.5.0
- Standardized all package versions to 0.5.0 across the monorepo
- Fixed driver-memory package.json paths for proper module resolution
- Ensured all packages are in sync for the 0.5.0 release

Patch Changes

Updated dependencies [b2df5f7]
- @objectstack/spec@0.6.0

0.4.2

Patch Changes

Unify all package versions to 0.4.2
Updated dependencies
- @objectstack/spec@0.4.2

0.4.1

Patch Changes

Version synchronization and dependency updates
- Synchronized plugin-msw version to 0.4.1
- Updated runtime peer dependency versions to ^0.4.1
- Fixed internal dependency version mismatches
Updated dependencies
- @objectstack/spec@0.4.1

0.4.0

Minor Changes

Release version 0.4.0

0.3.3

Patch Changes

Workflow and configuration improvements
- Enhanced GitHub workflows for CI, release, and PR automation
- Added comprehensive prompt templates for different protocol areas
- Improved project documentation and automation guides
- Updated changeset configuration
- Added cursor rules for better development experience
Updated dependencies
- @objectstack/spec@0.3.3

0.3.2

Patch Changes

Patch release for maintenance and stability improvements
Updated dependencies
- @objectstack/spec@0.3.2

0.3.1

Patch Changes

@objectstack/spec@0.3.1

0.3.0

Patch Changes

Updated dependencies
- @objectstack/spec@1.0.0

0.2.0

Minor Changes

Initial release of ObjectStack Protocol & Specification packages

This is the first public release of the ObjectStack ecosystem, providing:
- Core protocol definitions and TypeScript types
- ObjectQL query language and runtime
- Memory driver for in-memory data storage
- Client library for interacting with ObjectStack
- Hono server plugin for REST API endpoints
- Complete JSON schema generation for all specifications

Uh oh!

FilesExpand file tree

CHANGELOG.md

Latest commit

History

CHANGELOG.md

File metadata and controls

@objectstack/client

16.1.1

Patch Changes

16.1.0

Patch Changes

16.0.0

Minor Changes

Patch Changes

16.0.0-rc.1

Minor Changes

Patch Changes

16.0.0-rc.0

Minor Changes

Patch Changes

15.1.1

Patch Changes

15.1.0

Patch Changes

15.0.0

Patch Changes

14.8.0

Patch Changes

14.7.0

Patch Changes

14.6.0

Patch Changes

14.5.0

Patch Changes

14.4.0

Patch Changes

14.3.0

Patch Changes

14.2.0

Patch Changes

14.1.0

Patch Changes

14.0.0

Patch Changes

13.0.0

Patch Changes

12.6.0

Patch Changes

12.5.0

Patch Changes

12.4.0

Patch Changes

12.3.0

Patch Changes

12.2.0

Patch Changes

12.1.0

Patch Changes

12.0.0

Patch Changes

11.10.0

Patch Changes

11.9.0

Patch Changes

11.8.0

Patch Changes

11.7.0

Patch Changes

11.6.0

Patch Changes

11.5.0

Patch Changes

11.4.0

Patch Changes

11.3.0

Patch Changes

11.2.0

Patch Changes

11.1.0