chore: version packages#2662
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
July 6, 2026 22:44
666bc4e to
326a6f9
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/hono@12.4.1
Patch Changes
@objectstack/account@12.4.1
Patch Changes
@objectstack/setup@12.4.1
Patch Changes
@objectstack/studio@12.4.1
Patch Changes
@objectstack/cli@12.4.1
Patch Changes
3b9fd94:
os dev/os start/os serveno longer default-load the@objectstack/studioapp package.The console ships a dedicated Studio surface at
/_console/studio/<package-id>/<pillar>,so Studio no longer needs to exist as a navigable app tile in the home "Your apps" list.
The
@objectstack/studiopackage is unchanged and can still be registered explicitly;Setup and Account remain default-loaded (ADR-0048 one-app-per-package mechanism).
Updated dependencies [8b3d363]
@objectstack/client@12.4.1
Patch Changes
@objectstack/client-react@12.4.1
Patch Changes
@objectstack/cloud-connection@12.4.1
Patch Changes
@objectstack/connector-mcp@12.4.1
Patch Changes
@objectstack/connector-openapi@12.4.1
Patch Changes
@objectstack/connector-rest@12.4.1
Patch Changes
@objectstack/connector-slack@12.4.1
Patch Changes
@objectstack/core@12.4.1
Patch Changes
@objectstack/formula@12.4.1
Patch Changes
@objectstack/lint@12.4.1
Patch Changes
@objectstack/mcp@12.4.1
Patch Changes
@objectstack/metadata@12.4.1
Patch Changes
@objectstack/metadata-core@12.4.1
Patch Changes
@objectstack/metadata-fs@12.4.1
Patch Changes
@objectstack/metadata-protocol@12.4.1
Patch Changes
8b3d363: Package metadata seed can no longer wedge the platform via record-change automation.
A seeded record whose lifecycle flow self-triggered (a
record-after-updateflowwriting back to its own trigger record) looped forever when its boolean re-entry
guard never tripped — booleans persist as integer
1on SQLite/libsql and CEL1 != trueistrue. During first-boot seed (which awaits automation) this hungthe whole kernel build.
Three layers:
ExecutionContext.skipTriggers(set by the seed-loader, threaded ontoHookContext.sessionviabuildSession) makes the record-change trigger skipflow dispatch for seed/bulk writes — seed data is end-state reference data, not
user events. Lifecycle hooks still run.
coerceBooleanFields()converts SQLite 0/1 (and'0'/'1'/'true'/'false') toreal booleans on the after-hook view of a record (
hookContext.result/.previous), so flow conditions see JS booleans. The value returned to thecaller is unchanged.
execution is still on the stack (
activeRecordFlows), a backstop for anyself-trigger loop.
Updated dependencies [8b3d363]
@objectstack/objectql@12.4.1
Patch Changes
8b3d363: Package metadata seed can no longer wedge the platform via record-change automation.
A seeded record whose lifecycle flow self-triggered (a
record-after-updateflowwriting back to its own trigger record) looped forever when its boolean re-entry
guard never tripped — booleans persist as integer
1on SQLite/libsql and CEL1 != trueistrue. During first-boot seed (which awaits automation) this hungthe whole kernel build.
Three layers:
ExecutionContext.skipTriggers(set by the seed-loader, threaded ontoHookContext.sessionviabuildSession) makes the record-change trigger skipflow dispatch for seed/bulk writes — seed data is end-state reference data, not
user events. Lifecycle hooks still run.
coerceBooleanFields()converts SQLite 0/1 (and'0'/'1'/'true'/'false') toreal booleans on the after-hook view of a record (
hookContext.result/.previous), so flow conditions see JS booleans. The value returned to thecaller is unchanged.
execution is still on the stack (
activeRecordFlows), a backstop for anyself-trigger loop.
Updated dependencies [8b3d363]
@objectstack/observability@12.4.1
Patch Changes
@objectstack/platform-objects@12.4.1
Patch Changes
@objectstack/driver-memory@12.4.1
Patch Changes
@objectstack/driver-mongodb@12.4.1
Patch Changes
@objectstack/driver-sql@12.4.1
Patch Changes
@objectstack/driver-sqlite-wasm@12.4.1
Patch Changes
@objectstack/embedder-openai@12.4.1
Patch Changes
@objectstack/knowledge-memory@12.4.1
Patch Changes
@objectstack/knowledge-ragflow@12.4.1
Patch Changes
@objectstack/plugin-approvals@12.4.1
Patch Changes
@objectstack/plugin-audit@12.4.1
Patch Changes
@objectstack/plugin-auth@12.4.1
Patch Changes
@objectstack/plugin-dev@12.4.1
Patch Changes
3b9fd94:
os dev/os start/os serveno longer default-load the@objectstack/studioapp package.The console ships a dedicated Studio surface at
/_console/studio/<package-id>/<pillar>,so Studio no longer needs to exist as a navigable app tile in the home "Your apps" list.
The
@objectstack/studiopackage is unchanged and can still be registered explicitly;Setup and Account remain default-loaded (ADR-0048 one-app-per-package mechanism).
Updated dependencies [8b3d363]
@objectstack/plugin-email@12.4.1
Patch Changes
@objectstack/plugin-hono-server@12.4.1
Patch Changes
@objectstack/plugin-org-scoping@12.4.1
Patch Changes
@objectstack/plugin-reports@12.4.1
Patch Changes
@objectstack/plugin-security@12.4.1
Patch Changes
@objectstack/plugin-sharing@12.4.1
Patch Changes
@objectstack/plugin-webhooks@12.4.1
Patch Changes
@objectstack/rest@12.4.1
Patch Changes
@objectstack/runtime@12.4.1
Patch Changes
@objectstack/service-analytics@12.4.1
Patch Changes
@objectstack/service-automation@12.4.1
Patch Changes
8b3d363: Package metadata seed can no longer wedge the platform via record-change automation.
A seeded record whose lifecycle flow self-triggered (a
record-after-updateflowwriting back to its own trigger record) looped forever when its boolean re-entry
guard never tripped — booleans persist as integer
1on SQLite/libsql and CEL1 != trueistrue. During first-boot seed (which awaits automation) this hungthe whole kernel build.
Three layers:
ExecutionContext.skipTriggers(set by the seed-loader, threaded ontoHookContext.sessionviabuildSession) makes the record-change trigger skipflow dispatch for seed/bulk writes — seed data is end-state reference data, not
user events. Lifecycle hooks still run.
coerceBooleanFields()converts SQLite 0/1 (and'0'/'1'/'true'/'false') toreal booleans on the after-hook view of a record (
hookContext.result/.previous), so flow conditions see JS booleans. The value returned to thecaller is unchanged.
execution is still on the stack (
activeRecordFlows), a backstop for anyself-trigger loop.
Updated dependencies [8b3d363]
@objectstack/service-cache@12.4.1
Patch Changes
@objectstack/service-cluster@12.4.1
Patch Changes
@objectstack/service-cluster-redis@12.4.1
Patch Changes
@objectstack/service-datasource@12.4.1
Patch Changes
@objectstack/service-i18n@12.4.1
Patch Changes
@objectstack/service-job@12.4.1
Patch Changes
@objectstack/service-knowledge@12.4.1
Patch Changes
@objectstack/service-messaging@12.4.1
Patch Changes
@objectstack/service-package@12.4.1
Patch Changes
@objectstack/service-queue@12.4.1
Patch Changes
@objectstack/service-realtime@12.4.1
Patch Changes
@objectstack/service-settings@12.4.1
Patch Changes
@objectstack/service-storage@12.4.1
Patch Changes
@objectstack/spec@12.4.1
Patch Changes
8b3d363: Package metadata seed can no longer wedge the platform via record-change automation.
A seeded record whose lifecycle flow self-triggered (a
record-after-updateflowwriting back to its own trigger record) looped forever when its boolean re-entry
guard never tripped — booleans persist as integer
1on SQLite/libsql and CEL1 != trueistrue. During first-boot seed (which awaits automation) this hungthe whole kernel build.
Three layers:
ExecutionContext.skipTriggers(set by the seed-loader, threaded ontoHookContext.sessionviabuildSession) makes the record-change trigger skipflow dispatch for seed/bulk writes — seed data is end-state reference data, not
user events. Lifecycle hooks still run.
coerceBooleanFields()converts SQLite 0/1 (and'0'/'1'/'true'/'false') toreal booleans on the after-hook view of a record (
hookContext.result/.previous), so flow conditions see JS booleans. The value returned to thecaller is unchanged.
execution is still on the stack (
activeRecordFlows), a backstop for anyself-trigger loop.
@objectstack/trigger-api@12.4.1
Patch Changes
@objectstack/trigger-record-change@12.4.1
Patch Changes
8b3d363: Package metadata seed can no longer wedge the platform via record-change automation.
A seeded record whose lifecycle flow self-triggered (a
record-after-updateflowwriting back to its own trigger record) looped forever when its boolean re-entry
guard never tripped — booleans persist as integer
1on SQLite/libsql and CEL1 != trueistrue. During first-boot seed (which awaits automation) this hungthe whole kernel build.
Three layers:
ExecutionContext.skipTriggers(set by the seed-loader, threaded ontoHookContext.sessionviabuildSession) makes the record-change trigger skipflow dispatch for seed/bulk writes — seed data is end-state reference data, not
user events. Lifecycle hooks still run.
coerceBooleanFields()converts SQLite 0/1 (and'0'/'1'/'true'/'false') toreal booleans on the after-hook view of a record (
hookContext.result/.previous), so flow conditions see JS booleans. The value returned to thecaller is unchanged.
execution is still on the stack (
activeRecordFlows), a backstop for anyself-trigger loop.
Updated dependencies [8b3d363]
@objectstack/trigger-schedule@12.4.1
Patch Changes
@objectstack/types@12.4.1
Patch Changes
@objectstack/verify@12.4.1
Patch Changes
@objectstack/console@12.4.1
create-objectstack@12.4.1
@objectstack/sdui-parser@12.4.1
objectstack-vscode@12.4.1
@objectstack/example-crm@4.0.75
Patch Changes
@objectstack/example-showcase@0.2.21
Patch Changes
@objectstack/example-todo@4.0.75
Patch Changes
@objectstack/example-embed-objectql@0.0.15
Patch Changes
@objectstack/dogfood@0.0.23
Patch Changes
@objectstack/downstream-contract@0.0.21
Patch Changes