Repository navigation
chore: version packages - #1359
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
May 27, 2026 05:33
6598b03 to
e79efb3
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
May 27, 2026 05:47
d7629a0 to
7fc72fc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
May 27, 2026 06:09
7fc72fc to
7833234
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
May 27, 2026 06:18
7833234 to
f54481e
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/objectql@6.8.0
Minor Changes
c8b9f57: Metadata Admin engine — protocol foundations.
This is the backend half of the unified Metadata Admin shipped in the Setup
app. The framework now exposes everything the engine needs to render a
directory tile, schema-driven form, layered diff, references graph, and
destructive-change confirmation for every registered metadata type.
GET /api/v1/meta/typesis now type-rich. Each entry includes{ icon, domain, schema (JSONSchema), allowOrgOverride, allowRuntimeCreate, supportsOverlay, ui? }so the client can render without a second round-trip per type.
GET /api/v1/meta/:type/:name/referencesscans every registeredmetadata type for pointers to the given item (object fields, view sources,
flow targets, permission objects, …) and returns the inbound edges so the
UI can warn before deletes.
GET /api/v1/meta/:type/:name?layers=code,overlay,effectivereturnseach layer separately rather than the merged effective document, powering
the 3-state diff editor (code source / overlay / effective).
PUT /api/v1/meta/object/:nameandPUT /api/v1/meta/field/:name: rejects field type narrowing, requiredtoggled on without a default, removed enum values, etc., unless the
client opts in with
force=true.OBJECTSTACK_METADATA_WRITABLE=object,field,permission,view,…flips
allowOrgOverrideon for the listed types at boot, enablingruntime overlays for production without re-deploying spec.
walks through registry entry + Zod schema + optional custom editor.
Setup app navigation now uses the new component-route variant
(
{ type: 'component', componentRef: 'metadata:directory' }) — the temporary/dev/metaroute is removed.Patch Changes
@objectstack/platform-objects@6.8.0
Minor Changes
c8b9f57: Metadata Admin engine — protocol foundations.
This is the backend half of the unified Metadata Admin shipped in the Setup
app. The framework now exposes everything the engine needs to render a
directory tile, schema-driven form, layered diff, references graph, and
destructive-change confirmation for every registered metadata type.
GET /api/v1/meta/typesis now type-rich. Each entry includes{ icon, domain, schema (JSONSchema), allowOrgOverride, allowRuntimeCreate, supportsOverlay, ui? }so the client can render without a second round-trip per type.
GET /api/v1/meta/:type/:name/referencesscans every registeredmetadata type for pointers to the given item (object fields, view sources,
flow targets, permission objects, …) and returns the inbound edges so the
UI can warn before deletes.
GET /api/v1/meta/:type/:name?layers=code,overlay,effectivereturnseach layer separately rather than the merged effective document, powering
the 3-state diff editor (code source / overlay / effective).
PUT /api/v1/meta/object/:nameandPUT /api/v1/meta/field/:name: rejects field type narrowing, requiredtoggled on without a default, removed enum values, etc., unless the
client opts in with
force=true.OBJECTSTACK_METADATA_WRITABLE=object,field,permission,view,…flips
allowOrgOverrideon for the listed types at boot, enablingruntime overlays for production without re-deploying spec.
walks through registry entry + Zod schema + optional custom editor.
Setup app navigation now uses the new component-route variant
(
{ type: 'component', componentRef: 'metadata:directory' }) — the temporary/dev/metaroute is removed.45d27c5: Setup App: added a Data Model navigation group with Objects and
Fields entries that open filtered list views of
sys_metadata.To support the new entries,
sys_metadata.listViewsnow includesonly_objects,only_fields, andall_metadata— each filtered bytypeand projecting a curated column set (name, namespace, scope,managed_by, state, updated_at). The new list views are the read side of
the protocol-driven metadata editing flow; the matching write surface
is provided by
MetadataObjectsPage/MetadataFieldsPagein@object-ui/plugin-designer(separate package), which call theexisting
/api/v1/meta/*REST endpoints.No behavioural changes to the metadata REST endpoints themselves; no
migration required.
Patch Changes
@objectstack/rest@6.8.0
Minor Changes
c8b9f57: Metadata Admin engine — protocol foundations.
This is the backend half of the unified Metadata Admin shipped in the Setup
app. The framework now exposes everything the engine needs to render a
directory tile, schema-driven form, layered diff, references graph, and
destructive-change confirmation for every registered metadata type.
GET /api/v1/meta/typesis now type-rich. Each entry includes{ icon, domain, schema (JSONSchema), allowOrgOverride, allowRuntimeCreate, supportsOverlay, ui? }so the client can render without a second round-trip per type.
GET /api/v1/meta/:type/:name/referencesscans every registeredmetadata type for pointers to the given item (object fields, view sources,
flow targets, permission objects, …) and returns the inbound edges so the
UI can warn before deletes.
GET /api/v1/meta/:type/:name?layers=code,overlay,effectivereturnseach layer separately rather than the merged effective document, powering
the 3-state diff editor (code source / overlay / effective).
PUT /api/v1/meta/object/:nameandPUT /api/v1/meta/field/:name: rejects field type narrowing, requiredtoggled on without a default, removed enum values, etc., unless the
client opts in with
force=true.OBJECTSTACK_METADATA_WRITABLE=object,field,permission,view,…flips
allowOrgOverrideon for the listed types at boot, enablingruntime overlays for production without re-deploying spec.
walks through registry entry + Zod schema + optional custom editor.
Setup app navigation now uses the new component-route variant
(
{ type: 'component', componentRef: 'metadata:directory' }) — the temporary/dev/metaroute is removed.Patch Changes
@objectstack/service-ai@6.8.0
Minor Changes
6e88f77: Auto-persist chat history when a
conversationIdis supplied.AIService.chatWithToolsandstreamChatWithToolsnow write the inbound user turn, each intermediate assistant/tool round, and the final assistant turn toai_messageswhenevertoolExecutionContext.conversationIdis set. Persistence is best-effort: failures are warned and never break the chat response.IAIConversationService.update(conversationId, { title?, metadata? })and a matchingPATCH /api/v1/ai/conversations/:idroute so clients can rename conversations and edit metadata.ObjectQLConversationServiceandInMemoryConversationServiceboth implement the newupdatemethod.Patch Changes
50ccd9c: Fix peer-dependency version range from
workspace:*toworkspace:^to avoidforced major bumps in fixed-group releases.
workspace:*expands to an exactversion on publish; any minor bump of the peer then falls out of range and
triggers a semver-major bump on the dependent.
workspace:^expands to^x.y.zwhich correctly accepts minor bumps.
Affects:
service-aipeer on@objectstack/embedder-openairuntimepeer on@objectstack/driver-tursoUpdated dependencies [6e88f77]
Updated dependencies [c8b9f57]
@objectstack/spec@6.8.0
Minor Changes
c8b9f57: Metadata Admin engine — protocol foundations.
This is the backend half of the unified Metadata Admin shipped in the Setup
app. The framework now exposes everything the engine needs to render a
directory tile, schema-driven form, layered diff, references graph, and
destructive-change confirmation for every registered metadata type.
GET /api/v1/meta/typesis now type-rich. Each entry includes{ icon, domain, schema (JSONSchema), allowOrgOverride, allowRuntimeCreate, supportsOverlay, ui? }so the client can render without a second round-trip per type.
GET /api/v1/meta/:type/:name/referencesscans every registeredmetadata type for pointers to the given item (object fields, view sources,
flow targets, permission objects, …) and returns the inbound edges so the
UI can warn before deletes.
GET /api/v1/meta/:type/:name?layers=code,overlay,effectivereturnseach layer separately rather than the merged effective document, powering
the 3-state diff editor (code source / overlay / effective).
PUT /api/v1/meta/object/:nameandPUT /api/v1/meta/field/:name: rejects field type narrowing, requiredtoggled on without a default, removed enum values, etc., unless the
client opts in with
force=true.OBJECTSTACK_METADATA_WRITABLE=object,field,permission,view,…flips
allowOrgOverrideon for the listed types at boot, enablingruntime overlays for production without re-deploying spec.
walks through registry entry + Zod schema + optional custom editor.
Setup app navigation now uses the new component-route variant
(
{ type: 'component', componentRef: 'metadata:directory' }) — the temporary/dev/metaroute is removed.Patch Changes
6e88f77: Auto-persist chat history when a
conversationIdis supplied.AIService.chatWithToolsandstreamChatWithToolsnow write the inbound user turn, each intermediate assistant/tool round, and the final assistant turn toai_messageswhenevertoolExecutionContext.conversationIdis set. Persistence is best-effort: failures are warned and never break the chat response.IAIConversationService.update(conversationId, { title?, metadata? })and a matchingPATCH /api/v1/ai/conversations/:idroute so clients can rename conversations and edit metadata.ObjectQLConversationServiceandInMemoryConversationServiceboth implement the newupdatemethod.@objectstack/account@6.8.0
Patch Changes
endpoint is
/api/v1/auth/request-password-reset(not the legacyforget-password); the account UI now calls the correct path sothe reset email actually dispatches.
@objectstack/hono@6.8.0
Patch Changes
@objectstack/cli@6.8.0
Patch Changes
@objectstack/client@6.8.0
Patch Changes
@objectstack/client-react@6.8.0
Patch Changes
@objectstack/core@6.8.0
Patch Changes
@objectstack/formula@6.8.0
Patch Changes
@objectstack/metadata@6.8.0
Patch Changes
@objectstack/metadata-fs@6.8.0
Patch Changes
@objectstack/observability@6.8.0
Patch Changes
@objectstack/driver-memory@6.8.0
Patch Changes
@objectstack/driver-mongodb@6.8.0
Patch Changes
@objectstack/driver-sql@6.8.0
Patch Changes
@objectstack/driver-sqlite-wasm@6.8.0
Patch Changes
@objectstack/driver-turso@6.8.0
Patch Changes
@objectstack/embedder-openai@6.8.0
Patch Changes
@objectstack/knowledge-memory@6.8.0
Patch Changes
@objectstack/knowledge-ragflow@6.8.0
Patch Changes
@objectstack/knowledge-turso@6.8.0
Patch Changes
@objectstack/plugin-approvals@6.8.0
Patch Changes
@objectstack/plugin-audit@6.8.0
Patch Changes
@objectstack/plugin-auth@6.8.0
Patch Changes
@objectstack/plugin-dev@6.8.0
Patch Changes
@objectstack/plugin-email@6.8.0
Patch Changes
@objectstack/plugin-hono-server@6.8.0
Patch Changes
@objectstack/plugin-mcp-server@6.8.0
Patch Changes
@objectstack/plugin-msw@6.8.0
Patch Changes
@objectstack/plugin-reports@6.8.0
Patch Changes
@objectstack/plugin-security@6.8.0
Patch Changes
@objectstack/plugin-sharing@6.8.0
Patch Changes
@objectstack/plugin-webhooks@6.8.0
Patch Changes
@objectstack/runtime@6.8.0
Patch Changes
50ccd9c: Fix peer-dependency version range from
workspace:*toworkspace:^to avoidforced major bumps in fixed-group releases.
workspace:*expands to an exactversion on publish; any minor bump of the peer then falls out of range and
triggers a semver-major bump on the dependent.
workspace:^expands to^x.y.zwhich correctly accepts minor bumps.
Affects:
service-aipeer on@objectstack/embedder-openairuntimepeer on@objectstack/driver-tursoUpdated dependencies [6e88f77]
Updated dependencies [c8b9f57]
@objectstack/service-analytics@6.8.0
Patch Changes
@objectstack/service-automation@6.8.0
Patch Changes
@objectstack/service-cache@6.8.0
Patch Changes
@objectstack/service-cluster@6.8.0
Patch Changes
@objectstack/service-cluster-redis@6.8.0
Patch Changes
@objectstack/service-feed@6.8.0
Patch Changes
@objectstack/service-i18n@6.8.0
Patch Changes
@objectstack/service-job@6.8.0
Patch Changes
@objectstack/service-knowledge@6.8.0
Patch Changes
@objectstack/service-package@6.8.0
Patch Changes
@objectstack/service-queue@6.8.0
Patch Changes
@objectstack/service-realtime@6.8.0
Patch Changes
@objectstack/service-settings@6.8.0
Patch Changes
0a40bd1: Make the Settings UI survive crypto key changes and dev restarts.
Two related fixes to stop a single bad encrypted row (e.g. an AI API key
encrypted before a server restart) from 500-ing the entire
GET /api/settings/:namespaceendpoint withUnsupported state or unable to authenticate data:InMemoryCryptoProvidernow honours theOBJECTSTACK_DEV_CRYPTO_KEYenv var (32 bytes, hex or base64) as a stable AES-256-GCM data key.
When the env var is unset, the provider still generates an ephemeral
key but now logs the generated key once as base64 so dev operators
can paste it into
.envand survive subsequentpnpm devrestarts.Production behaviour (KMS-backed providers) is unchanged.
SettingsService.materialiseRownow catches decrypt failures,logs a single warning naming the offending
namespace.key, andreturns
nullinstead of throwing. The field renders as empty andremains editable, so operators can re-enter the secret in place
rather than being locked out of the settings page entirely.
Updated dependencies [6e88f77]
Updated dependencies [c8b9f57]
Updated dependencies [45d27c5]
@objectstack/service-storage@6.8.0
Patch Changes
@objectstack/types@6.8.0
Patch Changes
@objectstack/express@6.8.0
@objectstack/fastify@6.8.0
@objectstack/nestjs@6.8.0
@objectstack/nextjs@6.8.0
@objectstack/nuxt@6.8.0
@objectstack/sveltekit@6.8.0
create-objectstack@6.8.0
@objectstack/metadata-core@6.8.0
objectstack-vscode@6.8.0
@objectstack/example-crm@4.0.23
Patch Changes
@example/app-todo@4.0.23
Patch Changes