Uh oh!
There was an error while loading. Please reload this page.
chore: version packages - #1280
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actionsBotforce-pushed
the
changeset-release/main
branch
2 times, most recently
from
May 24, 2026 15:14
d27aaec to
6cf7d09Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 24, 2026 15:28
6cf7d09 to
fc9c6e7Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 25, 2026 01:06
fc9c6e7 to
d3f1c8dComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 25, 2026 01:23
d3f1c8d to
0f8d723Compare
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 freeto 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/account@6.1.2
Patch Changes
@objectstack/hono@6.1.2
Patch Changes
@objectstack/cli@6.1.2
Patch Changes
@objectstack/client@6.1.2
Patch Changes
@objectstack/client-react@6.1.2
Patch Changes
@objectstack/core@6.1.2
Patch Changes
@objectstack/formula@6.1.2
Patch Changes
@objectstack/metadata@6.1.2
Patch Changes
@objectstack/metadata-fs@6.1.2
Patch Changes
@objectstack/objectql@6.1.2
Patch Changes
@objectstack/observability@6.1.2
Patch Changes
@objectstack/platform-objects@6.1.2
Patch Changes
@objectstack/driver-memory@6.1.2
Patch Changes
@objectstack/driver-mongodb@6.1.2
Patch Changes
@objectstack/driver-sql@6.1.2
Patch Changes
@objectstack/driver-sqlite-wasm@6.1.2
Patch Changes
@objectstack/driver-turso@6.1.2
Patch Changes
@objectstack/plugin-approvals@6.1.2
Patch Changes
@objectstack/plugin-audit@6.1.2
Patch Changes
@objectstack/plugin-auth@6.1.2
Patch Changes
@objectstack/plugin-dev@6.1.2
Patch Changes
@objectstack/plugin-email@6.1.2
Patch Changes
@objectstack/plugin-hono-server@6.1.2
Patch Changes
@objectstack/plugin-mcp-server@6.1.2
Patch Changes
@objectstack/plugin-msw@6.1.2
Patch Changes
@objectstack/plugin-reports@6.1.2
Patch Changes
@objectstack/plugin-security@6.1.2
Patch Changes
@objectstack/plugin-sharing@6.1.2
Patch Changes
@objectstack/plugin-webhooks@6.1.2
Patch Changes
@objectstack/rest@6.1.2
Patch Changes
@objectstack/runtime@6.1.2
Patch Changes
@objectstack/service-ai@6.1.2
Patch Changes
13a4f38: Actions-as-tools Phase 2: the AI tool runtime can now dispatch
type:'api'andtype:'flow'actions in addition totype:'script'.ApiActionClientinterface andcreateFetchApiClient({ baseUrl, headers, fetch })factory — default fetch-based dispatch resolves relativetargetpaths againstbaseUrl, throws on non-2xx with${method} ${url} → ${status}: ${body}, and JSON-parses the response.buildApiRequestBody(action, args, record, recordId)helper — honoursbodyShape.wrap,recordIdParam+recordIdField(defaults to'id'), and mergesbodyExtralast so constants win.ActionToolsContextextended (additive):automation,apiClient,apiBaseUrl,apiHeaders.actionSkipReason()gains an optional secondctxparameter that returns precise wiring-availability reasons ('no automation service available','no apiClient or apiBaseUrl configured'). Studio-only types (url/modal/form) and all dangerous variants (confirmText,mode:'delete',variant:'danger') remain skipped.AIServicePluginoptions acceptapiActionBaseUrl(falls back toOS_AI_ACTION_API_BASE_URL) andapiActionHeaders; the plugin now resolves theautomationservice silently and threads everything intoregisterActionsAsTools.Net result: every non-destructive declarative action with a target —
script,api,flow— is now LLM-callable end-to-end as soon as the corresponding wiring is in place.449e35d: Real-LLM smoke test for the
data_chatagent loop, plus twoquery_datarobustness fixes shaken out by running it against
openai/gpt-4.1-miniviathe Vercel AI Gateway.
query_datatool fixesRemoved the LLM-controllable
modelparameter from the public toolschema. Frontier models were hallucinating
text-davinci-003and otherlong-dead model ids, breaking every plan generation.
Switched the structured-output filter shape from
z.record(...)(whichemits
propertyNamesin JSON Schema, rejected by OpenAI StructuredOutputs) to a
whereJsonstring field. The model emits a JSON-encodedObjectQL filter; the tool parses & validates it before execution. This
also fixes a parallel issue with OpenAI's strict mode requiring every
property to appear in
required.Switched all optional fields to
.nullable()so the planner Zod schemasatisfies OpenAI Structured Outputs' "every property must be required"
rule.
Beefed up the planner system prompt with explicit operator hints — most
importantly: use
$containsfor partial string matches ("task named Foo"→{"subject":{"$contains":"Foo"}}), not equality. Without thishint the model defaulted to exact-match equality and never found
anything.
New smoke test
examples/app-todo/test/ai-llm.test.ts(gated onAI_GATEWAY_API_KEY):boots the full ObjectStack, registers
query_data+ the six auto-generatedaction_*tools, sends "Please mark the 'Build' task as complete." to areal LLM, and asserts that
the model picked the right tools in the right order
(
query_data→action_complete_task),a task row actually flipped to
completed, andan
ai_traceschat_with_toolsrow landed.Run with:
pnpm --filter @example/app-todo test:llm.Verified end-to-end against
openai/gpt-4.1-mini(~6.6 s, 2 tool calls,1 task completed, trace persisted).
@objectstack/service-analytics@6.1.2
Patch Changes
@objectstack/service-automation@6.1.2
Patch Changes
@objectstack/service-cache@6.1.2
Patch Changes
@objectstack/service-cluster@5.1.5
Patch Changes
@objectstack/service-cluster-redis@5.1.5
Patch Changes
@objectstack/service-feed@6.1.2
Patch Changes
@objectstack/service-i18n@6.1.2
Patch Changes
@objectstack/service-job@6.1.2
Patch Changes
@objectstack/service-package@6.1.2
Patch Changes
@objectstack/service-queue@6.1.2
Patch Changes
@objectstack/service-realtime@6.1.2
Patch Changes
@objectstack/service-settings@6.1.2
Patch Changes
@objectstack/service-storage@6.1.2
Patch Changes
@objectstack/types@6.1.2
Patch Changes
@objectstack/express@6.1.2
@objectstack/fastify@6.1.2
@objectstack/nestjs@6.1.2
@objectstack/nextjs@6.1.2
@objectstack/nuxt@6.1.2
@objectstack/sveltekit@6.1.2
create-objectstack@6.1.2
@objectstack/metadata-core@6.1.2
@objectstack/spec@6.1.2
objectstack-vscode@6.1.2
@objectstack/example-crm@4.0.15
Patch Changes
@example/app-todo@4.0.15
Patch Changes
449e35d: Real-LLM smoke test for the
data_chatagent loop, plus twoquery_datarobustness fixes shaken out by running it against
openai/gpt-4.1-miniviathe Vercel AI Gateway.
query_datatool fixesRemoved the LLM-controllable
modelparameter from the public toolschema. Frontier models were hallucinating
text-davinci-003and otherlong-dead model ids, breaking every plan generation.
Switched the structured-output filter shape from
z.record(...)(whichemits
propertyNamesin JSON Schema, rejected by OpenAI StructuredOutputs) to a
whereJsonstring field. The model emits a JSON-encodedObjectQL filter; the tool parses & validates it before execution. This
also fixes a parallel issue with OpenAI's strict mode requiring every
property to appear in
required.Switched all optional fields to
.nullable()so the planner Zod schemasatisfies OpenAI Structured Outputs' "every property must be required"
rule.
Beefed up the planner system prompt with explicit operator hints — most
importantly: use
$containsfor partial string matches ("task named Foo"→{"subject":{"$contains":"Foo"}}), not equality. Without thishint the model defaulted to exact-match equality and never found
anything.
New smoke test
examples/app-todo/test/ai-llm.test.ts(gated onAI_GATEWAY_API_KEY):boots the full ObjectStack, registers
query_data+ the six auto-generatedaction_*tools, sends "Please mark the 'Build' task as complete." to areal LLM, and asserts that
the model picked the right tools in the right order
(
query_data→action_complete_task),a task row actually flipped to
completed, andan
ai_traceschat_with_toolsrow landed.Run with:
pnpm --filter @example/app-todo test:llm.Verified end-to-end against
openai/gpt-4.1-mini(~6.6 s, 2 tool calls,1 task completed, trace persisted).
Updated dependencies [13a4f38]
Updated dependencies [449e35d]