chore: version packages#1576
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
66c053d to
b246187
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
b246187 to
9633bcc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
9633bcc to
03dee02
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
03dee02 to
3e2b5ad
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
3e2b5ad to
e4b2961
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
e4b2961 to
58bb1dd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
58bb1dd to
c399985
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
c399985 to
044165a
Compare
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
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/service-messaging@7.10.0
Minor Changes
9f311f8: feat(messaging): digest batching for notifications (ADR-0030 P3b-2)
Recipients can now batch a topic into a
daily/weeklydigest instead ofreceiving every notification immediately. Builds on P3b-1's deferral seam:
PreferenceResolverconsumes thedigestpreference field anddigestDeferral()defers a batched recipient to the next window (local midnight / Monday 00:00),
tagging the target with a stable
window. Digest takes precedence overquiet-hours;
criticaland mandatory topics bypass it.sys_notification_deliverygains adigest_key(recipient|channel|window).Batched rows partition by that key so a window's rows co-locate, and the normal
outbox
claim()skips them while the newclaimDigest()drains a window whole.(recipient, channel, window)groupinto one
renderDigest()message under the existing per-partition cluster lock,then acks every row in the group with that single outcome.
Additive: non-digest notifications are unchanged. Timezone-from-
sys_user,configurable send-hour, and MJML digest emails are deferred follow-ups.
Patch Changes
@objectstack/express@7.10.0
Patch Changes
@objectstack/fastify@7.10.0
Patch Changes
@objectstack/hono@7.10.0
Patch Changes
e15c845: feat(hono): re-export the
Honotype from@objectstack/honoDownstream apps that consume
createHonoApp()only need theHonotype toannotate the returned app. They can now
import type { Hono } from '@objectstack/hono'instead of adding their own
honodependency, which guarantees a singlehonoacross alink:/cross-package boundary (no duplicate-packagetype-identity errors, no version-pin alignment).
honoremains a normalruntime dependency of this package, so standalone usage is unaffected.
@objectstack/nestjs@7.10.0
Patch Changes
@objectstack/nextjs@7.10.0
Patch Changes
@objectstack/nuxt@7.10.0
Patch Changes
@objectstack/sveltekit@7.10.0
Patch Changes
@objectstack/cli@7.10.0
Patch Changes
@objectstack/client@7.10.0
Patch Changes
@objectstack/client-react@7.10.0
Patch Changes
@objectstack/connector-mcp@7.10.0
Patch Changes
@objectstack/connector-openapi@7.10.0
Patch Changes
@objectstack/connector-rest@7.10.0
Patch Changes
@objectstack/connector-slack@7.10.0
Patch Changes
@objectstack/core@7.10.0
Patch Changes
@objectstack/formula@7.10.0
Patch Changes
@objectstack/metadata@7.10.0
Patch Changes
@objectstack/metadata-core@7.10.0
Patch Changes
@objectstack/metadata-fs@7.10.0
Patch Changes
@objectstack/objectql@7.10.0
Patch Changes
@objectstack/observability@7.10.0
Patch Changes
@objectstack/platform-objects@7.10.0
Patch Changes
@objectstack/driver-memory@7.10.0
Patch Changes
@objectstack/driver-mongodb@7.10.0
Patch Changes
@objectstack/driver-sql@7.10.0
Patch Changes
@objectstack/driver-sqlite-wasm@7.10.0
Patch Changes
@objectstack/embedder-openai@7.10.0
Patch Changes
@objectstack/knowledge-memory@7.10.0
Patch Changes
@objectstack/knowledge-ragflow@7.10.0
Patch Changes
@objectstack/plugin-approvals@7.10.0
Patch Changes
@objectstack/plugin-audit@7.10.0
Patch Changes
@objectstack/plugin-auth@7.10.0
Patch Changes
@objectstack/plugin-dev@7.10.0
Patch Changes
@objectstack/plugin-email@7.10.0
Patch Changes
@objectstack/plugin-hono-server@7.10.0
Patch Changes
@objectstack/plugin-mcp-server@7.10.0
Patch Changes
@objectstack/plugin-msw@7.10.0
Patch Changes
@objectstack/plugin-org-scoping@7.10.0
Patch Changes
@objectstack/plugin-reports@7.10.0
Patch Changes
@objectstack/plugin-security@7.10.0
Patch Changes
@objectstack/plugin-sharing@7.10.0
Patch Changes
@objectstack/plugin-trigger-record-change@7.10.0
Patch Changes
@objectstack/plugin-trigger-schedule@7.10.0
Patch Changes
@objectstack/plugin-webhooks@7.10.0
Patch Changes
@objectstack/rest@7.10.0
Patch Changes
@objectstack/runtime@7.10.0
Patch Changes
@objectstack/service-ai@7.10.0
Patch Changes
a46c017: feat(ai): actions opt in to being AI tools via an
ai:block (ADR-0011)Realigns ADR-0011 with its original opt-in design. An Action becomes an
AI-callable tool only when its metadata sets
ai.exposed: true, which requiresan explicit, LLM-facing
ai.description(≥40 chars, distinct from the UIlabel). There is no heuristic auto-exposure and no description derived fromthe label — a clean break from the first implementation's opt-out
aiExposedflag, which is removed (no compatibility shim; the platform has not shipped).
The
ai:block also carriescategory,paramHints(per-parameter JSON-Schemarefinement),
outputSchema(summarised into the tool description for chaining),and
requiresConfirmation(overrides the destructive-action HITL default).AIToolDefinitionis extended to carrycategory/outputSchema/objectName/
requiresConfirmation. The@objectstack/service-aibridge(
action-tools.ts) now gates on opt-in, mergesparamHints, and emits a lintwarning when an exposed destructive-looking action asserts itself safe via
ai.requiresConfirmation: false.Updated dependencies [a46c017]
Updated dependencies [3306d2f]
Updated dependencies [bc44195]
@objectstack/service-analytics@7.10.0
Patch Changes
@objectstack/service-automation@7.10.0
Patch Changes
3306d2f: feat(automation): surface structured-region body steps in run observability (Surface per-iteration / per-region step logs in run observability (ADR-0031 follow-up) #1505)
loop/parallel/try_catchpreviously ran their body, branch, and handlerregions against a region-local step log that was discarded — run logs
(
listRuns/getRun) showed the container as a single opaque step, hiding theper-iteration / per-branch steps that actually executed.
AutomationEngine.runRegion()now returns its body steps, and the containernode folds them into the parent run log via a new
NodeExecutionResult.childStepsfield. Each surfaced step is tagged with its immediate container via three new
optional fields on
ExecutionStepLogSchema(and the engine'sStepLogEntry):parentNodeId— the enclosingloop/parallel/try_catchnodeiteration— zero-based loop iteration or parallel branch indexregionKind—loop-body|parallel-branch|try|catchTagging fills only fields left undefined, so nested regions keep each step's
innermost container. A failed try-region attempt's partial steps are still not
surfaced (preserving
try_catchretry semantics). Fully additive — existing runlogs and consumers are unaffected.
bc44195: chore(automation): retire the
workflow_ruleauthoring paradigm (ADR-0018 M5 dropped)ADR-0019 already removed the Workflow-Rule → Flow compiler (Workflow Rules were
removed in refactor(automation): remove Workflow Rules; reclaim
workflowfor state machines #1398 andworkflowwas reclaimed for state machines), but theworkflow_ruleparadigm tag survived inActionParadigmSchemaand on everybuilt-in node descriptor. There is no declarative Workflow-Rule authoring view
to feed, so the tag is now retired:
ActionParadigmSchemakeeps['flow', 'approval'], and thehttp/notify/connector_actiondescriptors (plusthe deprecated-alias fallback) advertise
['flow', 'approval']. Approvalexecution convergence is delivered by the ADR-0019 approval Flow node, not a
compiler. ADR-0018's status and migration table are updated to mark M3 shipped,
M4 framework-complete, and M5 dropped.
Updated dependencies [a46c017]
Updated dependencies [3306d2f]
Updated dependencies [bc44195]
@objectstack/service-cache@7.10.0
Patch Changes
@objectstack/service-cluster@7.10.0
Patch Changes
@objectstack/service-cluster-redis@7.10.0
Patch Changes
@objectstack/service-datasource@7.10.0
Patch Changes
@objectstack/service-feed@7.10.0
Patch Changes
@objectstack/service-i18n@7.10.0
Patch Changes
@objectstack/service-job@7.10.0
Patch Changes
@objectstack/service-knowledge@7.10.0
Patch Changes
@objectstack/service-package@7.10.0
Patch Changes
@objectstack/service-queue@7.10.0
Patch Changes
@objectstack/service-realtime@7.10.0
Patch Changes
@objectstack/service-settings@7.10.0
Patch Changes
@objectstack/service-storage@7.10.0
Patch Changes
@objectstack/spec@7.10.0
Patch Changes
a46c017: feat(ai): actions opt in to being AI tools via an
ai:block (ADR-0011)Realigns ADR-0011 with its original opt-in design. An Action becomes an
AI-callable tool only when its metadata sets
ai.exposed: true, which requiresan explicit, LLM-facing
ai.description(≥40 chars, distinct from the UIlabel). There is no heuristic auto-exposure and no description derived fromthe label — a clean break from the first implementation's opt-out
aiExposedflag, which is removed (no compatibility shim; the platform has not shipped).
The
ai:block also carriescategory,paramHints(per-parameter JSON-Schemarefinement),
outputSchema(summarised into the tool description for chaining),and
requiresConfirmation(overrides the destructive-action HITL default).AIToolDefinitionis extended to carrycategory/outputSchema/objectName/
requiresConfirmation. The@objectstack/service-aibridge(
action-tools.ts) now gates on opt-in, mergesparamHints, and emits a lintwarning when an exposed destructive-looking action asserts itself safe via
ai.requiresConfirmation: false.3306d2f: feat(automation): surface structured-region body steps in run observability (Surface per-iteration / per-region step logs in run observability (ADR-0031 follow-up) #1505)
loop/parallel/try_catchpreviously ran their body, branch, and handlerregions against a region-local step log that was discarded — run logs
(
listRuns/getRun) showed the container as a single opaque step, hiding theper-iteration / per-branch steps that actually executed.
AutomationEngine.runRegion()now returns its body steps, and the containernode folds them into the parent run log via a new
NodeExecutionResult.childStepsfield. Each surfaced step is tagged with its immediate container via three new
optional fields on
ExecutionStepLogSchema(and the engine'sStepLogEntry):parentNodeId— the enclosingloop/parallel/try_catchnodeiteration— zero-based loop iteration or parallel branch indexregionKind—loop-body|parallel-branch|try|catchTagging fills only fields left undefined, so nested regions keep each step's
innermost container. A failed try-region attempt's partial steps are still not
surfaced (preserving
try_catchretry semantics). Fully additive — existing runlogs and consumers are unaffected.
bc44195: chore(automation): retire the
workflow_ruleauthoring paradigm (ADR-0018 M5 dropped)ADR-0019 already removed the Workflow-Rule → Flow compiler (Workflow Rules were
removed in refactor(automation): remove Workflow Rules; reclaim
workflowfor state machines #1398 andworkflowwas reclaimed for state machines), but theworkflow_ruleparadigm tag survived inActionParadigmSchemaand on everybuilt-in node descriptor. There is no declarative Workflow-Rule authoring view
to feed, so the tag is now retired:
ActionParadigmSchemakeeps['flow', 'approval'], and thehttp/notify/connector_actiondescriptors (plusthe deprecated-alias fallback) advertise
['flow', 'approval']. Approvalexecution convergence is delivered by the ADR-0019 approval Flow node, not a
compiler. ADR-0018's status and migration table are updated to mark M3 shipped,
M4 framework-complete, and M5 dropped.
@objectstack/types@7.10.0
Patch Changes
@objectstack/account@7.10.0
@objectstack/console@7.10.0
create-objectstack@7.10.0
objectstack-vscode@7.10.0
@objectstack/example-crm@4.0.38
Patch Changes
@objectstack/example-showcase@0.1.8
Patch Changes
@example/app-todo@4.0.38
Patch Changes