chore: version packages#2602
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-actions
Bot
force-pushed
the
changeset-release/main
branch
from
daf1d0e to
a5f1de3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
a5f1de3 to
11762cd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
11762cd to
9a700e5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
9a700e5 to
d7a5354
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
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/runtime@12.1.0
Minor Changes
497bda8: feat(automation): honor flow deployment status for enable/disable + expose runtime enable/bound state
The engine bound and ran every registered flow, ignoring the flow's
persisted
status— so an author had no way to turn an automation off (short ofdeleting it) and no way to see whether one was actually live. This is the engine
half of the Studio's "clear on/off switch + visible enabled/bound status".
registerFlownow honorsstatus: a flow whose deploymentstatusisobsoleteorinvalidis treated as disabled — its trigger is not boundand
execute()refuses it.draft/active— and any legacy flow with noexplicit status — stay enabled, so existing flows are unaffected (zero
regression; this is the on/off switch persisting via the existing
statusfield, applied on the next publish rebind). A status flip back OUT of a
disabled state re-enables on re-register even if the flow had been turned off;
a runtime
toggleFlow()override on a still-enabled flow is preserved.New
getFlowRuntimeStates()+GET /api/v1/automation/_status: returns[{ name, enabled, bound }]for every registered flow — the truth behind theStudio's status badges (persisted
statusis metadata; whether a flow isactually enabled and wired to its trigger is engine state). Underscore-prefixed
so no flow name can shadow the route; degrades to an empty list on an older
service.
Tests cover: draft/active flows bind + enable (unchanged), an
obsoleteflow isneither bound nor enabled and
execute()refuses it, a status flipobsolete→active re-enables + re-binds, and the
_statusroute shape.Patch Changes
@objectstack/service-automation@12.1.0
Minor Changes
8bcd994: Automation run observability follow-ups (Automation run observability — follow-ups (retention, discoverable Runs surface, durable run detail) #2585): retention for
sys_automation_runrun history, and durable single-run detail.Retention (closes the unbounded-growth risk feat(automation): durable run history with failure reasons (run observability) #2581 introduced). Terminal run-history rows are now bounded by default, ADR-0057 posture:
runHistoryMaxPerFlow,0disables).runHistoryRetentionDays,0disables;runHistorySweepMstunes the interval, default 1 h).paused) rows are live resumable state and are never pruned.Durable single-run detail.
AutomationEngine.getRun(runId)now falls back to the durable history row when the run is no longer in the in-memory buffer (e.g. after a restart), and terminal rows persist a bounded per-node step log (steps_json: newest 200 steps, stacks stripped, 64 KB cap) — so "open a past failed run and see which node blew up" survives a restart. NewSuspendedRunStore.loadTerminal(runId)backs this;RunRecordgainsfinishedAtandsteps.497bda8: feat(automation): honor flow deployment status for enable/disable + expose runtime enable/bound state
The engine bound and ran every registered flow, ignoring the flow's
persisted
status— so an author had no way to turn an automation off (short ofdeleting it) and no way to see whether one was actually live. This is the engine
half of the Studio's "clear on/off switch + visible enabled/bound status".
registerFlownow honorsstatus: a flow whose deploymentstatusisobsoleteorinvalidis treated as disabled — its trigger is not boundand
execute()refuses it.draft/active— and any legacy flow with noexplicit status — stay enabled, so existing flows are unaffected (zero
regression; this is the on/off switch persisting via the existing
statusfield, applied on the next publish rebind). A status flip back OUT of a
disabled state re-enables on re-register even if the flow had been turned off;
a runtime
toggleFlow()override on a still-enabled flow is preserved.New
getFlowRuntimeStates()+GET /api/v1/automation/_status: returns[{ name, enabled, bound }]for every registered flow — the truth behind theStudio's status badges (persisted
statusis metadata; whether a flow isactually enabled and wired to its trigger is engine state). Underscore-prefixed
so no flow name can shadow the route; degrades to an empty list on an older
service.
Tests cover: draft/active flows bind + enable (unchanged), an
obsoleteflow isneither bound nor enabled and
execute()refuses it, a status flipobsolete→active re-enables + re-binds, and the
_statusroute shape.Patch Changes
@objectstack/hono@12.1.0
Patch Changes
@objectstack/account@12.1.0
Patch Changes
@objectstack/setup@12.1.0
Patch Changes
@objectstack/studio@12.1.0
Patch Changes
@objectstack/cli@12.1.0
Patch Changes
@objectstack/client@12.1.0
Patch Changes
@objectstack/client-react@12.1.0
Patch Changes
@objectstack/cloud-connection@12.1.0
Patch Changes
@objectstack/connector-mcp@12.1.0
Patch Changes
@objectstack/connector-openapi@12.1.0
Patch Changes
@objectstack/connector-rest@12.1.0
Patch Changes
@objectstack/connector-slack@12.1.0
Patch Changes
@objectstack/core@12.1.0
Patch Changes
@objectstack/formula@12.1.0
Patch Changes
@objectstack/lint@12.1.0
Patch Changes
@objectstack/mcp@12.1.0
Patch Changes
@objectstack/metadata@12.1.0
Patch Changes
@objectstack/metadata-core@12.1.0
Patch Changes
@objectstack/metadata-fs@12.1.0
Patch Changes
@objectstack/metadata-protocol@12.1.0
Patch Changes
@objectstack/objectql@12.1.0
Patch Changes
@objectstack/observability@12.1.0
Patch Changes
@objectstack/platform-objects@12.1.0
Patch Changes
@objectstack/driver-memory@12.1.0
Patch Changes
@objectstack/driver-mongodb@12.1.0
Patch Changes
@objectstack/driver-sql@12.1.0
Patch Changes
@objectstack/driver-sqlite-wasm@12.1.0
Patch Changes
@objectstack/embedder-openai@12.1.0
Patch Changes
@objectstack/knowledge-memory@12.1.0
Patch Changes
@objectstack/knowledge-ragflow@12.1.0
Patch Changes
@objectstack/plugin-approvals@12.1.0
Patch Changes
@objectstack/plugin-audit@12.1.0
Patch Changes
@objectstack/plugin-auth@12.1.0
Patch Changes
@objectstack/plugin-dev@12.1.0
Patch Changes
@objectstack/plugin-email@12.1.0
Patch Changes
@objectstack/plugin-hono-server@12.1.0
Patch Changes
@objectstack/plugin-org-scoping@12.1.0
Patch Changes
@objectstack/plugin-reports@12.1.0
Patch Changes
@objectstack/plugin-security@12.1.0
Patch Changes
@objectstack/plugin-sharing@12.1.0
Patch Changes
@objectstack/plugin-webhooks@12.1.0
Patch Changes
@objectstack/rest@12.1.0
Patch Changes
@objectstack/service-analytics@12.1.0
Patch Changes
@objectstack/service-cache@12.1.0
Patch Changes
@objectstack/service-cluster@12.1.0
Patch Changes
@objectstack/service-cluster-redis@12.1.0
Patch Changes
@objectstack/service-datasource@12.1.0
Patch Changes
@objectstack/service-i18n@12.1.0
Patch Changes
@objectstack/service-job@12.1.0
Patch Changes
@objectstack/service-knowledge@12.1.0
Patch Changes
@objectstack/service-messaging@12.1.0
Patch Changes
@objectstack/service-package@12.1.0
Patch Changes
@objectstack/service-queue@12.1.0
Patch Changes
@objectstack/service-realtime@12.1.0
Patch Changes
@objectstack/service-settings@12.1.0
Patch Changes
@objectstack/service-storage@12.1.0
Patch Changes
@objectstack/spec@12.1.0
Patch Changes
Field.relatedListJSDoc +.describe()to match the shipped behavior (详情页相关子表：降低对自定义 page 的依赖（relatedList 三态 + 列派生 + 确定性排序） #2579 follow-up). Non-primary related lists stack under a single shared "Related" tab and only'primary'earns its own tab — there is no count-based auto-split (the "count-aware" wording was a stale draft). Comment/description only; no code or behavior change.@objectstack/trigger-api@12.1.0
Patch Changes
@objectstack/trigger-record-change@12.1.0
Patch Changes
@objectstack/trigger-schedule@12.1.0
Patch Changes
@objectstack/types@12.1.0
Patch Changes
@objectstack/verify@12.1.0
Patch Changes
@objectstack/console@12.1.0
create-objectstack@12.1.0
@objectstack/sdui-parser@12.1.0
objectstack-vscode@12.1.0
@objectstack/example-crm@4.0.71
Patch Changes
@objectstack/example-showcase@0.2.17
Patch Changes
@objectstack/example-todo@4.0.71
Patch Changes
@objectstack/example-embed-objectql@0.0.11
Patch Changes
@objectstack/dogfood@0.0.19
Patch Changes
@objectstack/downstream-contract@0.0.17
Patch Changes