chore: release packages#2663
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 18, 2026 15:48
3f1a9f9 to
7c463dd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 18, 2026 16:42
7c463dd to
d1aa7d1
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
@object-ui/app-shell@16.1.0
Minor Changes
12390de: feat(studio): nest per-iteration / per-region step logs in the flow Runs panel (refactor: unify runtime dashboard editor onto studio's spec-driven inspectors #1505)
The run-observability
FlowRunsPanel(Studio → flow preview → Runs) rendered arun's step log as a flat list, so a
loopcontainer showed as a single step andits body steps — one set per iteration — appeared as an undifferentiated repeat
of the same node ids, with
parallelbranches andtry/catchhandlerslikewise flattened. The automation engine already tags each structured-region
body step with its container (
parentNodeId) plus aniteration/regionKind(ADR-0031, framework refactor: unify runtime dashboard editor onto studio's spec-driven inspectors #1505); the panel ignored those fields.
FlowRunsPanelnow reconstructs the execution tree from the flat, pre-order steplog (
buildStepTree) and nests body steps under their container node, grouped bya per-iteration / per-branch / handler header (
Iteration 2,Branch 1,Try,Catch). The reconstruction is robust to repeated node ids (a loop body noderuns once per iteration) and to regions nested inside regions, and degrades
safely — a body step whose container was dropped by durable-history truncation
still surfaces at the top level rather than vanishing.
276c6ba: feat(flow-designer): first-class panel for the time-relative trigger (chore(home): remove redundant "Make this home yours" empty-state card #1874)
The flow designer's start-node inspector now offers a Time-relative (date sweep)
trigger option alongside record / schedule triggers. Picking it reveals typed
fields for the backend's
config.timeRelativedescriptor — Sweep object, Datefield, Within days (range mode), Offset days (T-minus mode), an Extra filter, and
Max records — instead of hand-writing the block in the Advanced JSON editor. The
per-record Entry condition is available too.
Adds a
numberListconfig-field kind (a string-list editor that commitsnumber[]), so Offset days authors emit numbers rather than strings — keepingthe backend schema (
z.array(z.number())) strict rather than coercing on theconsumer side. All fields live under the nested
config.timeRelativeblock, whichthe group fully owns, so it never double-renders in Advanced JSON.
Patch Changes
8b8b744: chore(deps): align
@objectstack/formula/lint/clientto^15.1.1These three were still pinned to
^14.6.0while@objectstack/specwas already^15.1.1— a version skew from the v15 upgrade (formula/lint/client publish inlockstep with spec, and their own 15.0.0 entries are pure dependency bumps, so
this is alignment, not a behavioral migration).
Practical effect: the client-side field-rule evaluation
(
visibleWhen/readonlyWhen/requiredWhenviafieldRules.ts, which delegatesto
@objectstack/formula'sExpressionEngine) now tracks the 15.x engine — andwill pick up the framework's
dateField == today()equality fix(feat(formula):
dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) automatically at the next 15.x release via thecaret range. Renderer/action
visible/disabledpredicates are unaffected (theyuse the home-grown JS evaluator — tracked separately in Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661).Updated dependencies [8b8b744]
Updated dependencies [2e7d7f0]
@object-ui/core@16.1.0
Minor Changes
2e7d7f0: feat(evaluator): route
{ dialect: 'cel' }component/action predicates to the canonical CEL engine (Renderer/actionvisible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661)Component and action
visible/disabled/hiddenpredicates were evaluatedby the home-grown JS
ExpressionEvaluator, while field rules(
visibleWhen/readonlyWhen/requiredWhen, viafieldRules.ts) and row/listconditionals (via
evalRowPredicate) already delegate to the canonical@objectstack/formulaengine. That split meant a{ dialect: 'cel' }predicatein a renderer/action surface was executed as JavaScript — CEL-only forms
(
x in list,has(), typed==, thetoday()/daysFromNow()catalog) behaveddifferently from, or faulted against, the server's enforcement.
This converges the remaining tier onto the same engine:
@object-ui/core—ExpressionEvaluator.evaluateConditionnow detects a{ dialect: 'cel', source }envelope and evaluates it on@objectstack/formula(via
evalFieldPredicate), binding therecordnamespace plus the wholecontext bag as top-level scope (
record.*,features.*,user.*,app.*).Fail-soft to visible/enabled to match the legacy default;
throwOnErrorcallers still fail closed on a faulting predicate (a genuine
falseneverthrows). This fixes every
SchemaRenderervisibility/disabled read at once.@object-ui/react—toPredicateInputpreserves a CEL envelope instead ofcollapsing it to a
${source}string, anduseConditionaccepts and forwardsthe envelope (keyed on a stable
(dialect, source)so it doesn't re-evaluateeach render). Action buttons (
action-icon/group/bar/button) thereforeevaluate CEL
visible/enabled/disabledon the canonical engine.Back-compat: bare strings and
${…}templates stay on the legacy JS path(deprecation window); only an explicit
{ dialect: 'cel' }envelope is rerouted.{ dialect: 'template' }is unaffected.Together with the
^15.1.1alignment (chore(deps): align @objectstack/formula|lint|client to ^15.1.1 (spec skew) #2662), a renderer CEL predicate nowreaches the identical verdict as the server — including the framework's
dateField == today()equality fix (feat(formula):dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) once itlands in a published 15.x. The broader home-grown-vs-canonical divergence
motivation is Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661.Patch Changes
8b8b744: chore(deps): align
@objectstack/formula/lint/clientto^15.1.1These three were still pinned to
^14.6.0while@objectstack/specwas already^15.1.1— a version skew from the v15 upgrade (formula/lint/client publish inlockstep with spec, and their own 15.0.0 entries are pure dependency bumps, so
this is alignment, not a behavioral migration).
Practical effect: the client-side field-rule evaluation
(
visibleWhen/readonlyWhen/requiredWhenviafieldRules.ts, which delegatesto
@objectstack/formula'sExpressionEngine) now tracks the 15.x engine — andwill pick up the framework's
dateField == today()equality fix(feat(formula):
dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) automatically at the next 15.x release via thecaret range. Renderer/action
visible/disabledpredicates are unaffected (theyuse the home-grown JS evaluator — tracked separately in Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661).@object-ui/react@16.1.0
Minor Changes
2e7d7f0: feat(evaluator): route
{ dialect: 'cel' }component/action predicates to the canonical CEL engine (Renderer/actionvisible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661)Component and action
visible/disabled/hiddenpredicates were evaluatedby the home-grown JS
ExpressionEvaluator, while field rules(
visibleWhen/readonlyWhen/requiredWhen, viafieldRules.ts) and row/listconditionals (via
evalRowPredicate) already delegate to the canonical@objectstack/formulaengine. That split meant a{ dialect: 'cel' }predicatein a renderer/action surface was executed as JavaScript — CEL-only forms
(
x in list,has(), typed==, thetoday()/daysFromNow()catalog) behaveddifferently from, or faulted against, the server's enforcement.
This converges the remaining tier onto the same engine:
@object-ui/core—ExpressionEvaluator.evaluateConditionnow detects a{ dialect: 'cel', source }envelope and evaluates it on@objectstack/formula(via
evalFieldPredicate), binding therecordnamespace plus the wholecontext bag as top-level scope (
record.*,features.*,user.*,app.*).Fail-soft to visible/enabled to match the legacy default;
throwOnErrorcallers still fail closed on a faulting predicate (a genuine
falseneverthrows). This fixes every
SchemaRenderervisibility/disabled read at once.@object-ui/react—toPredicateInputpreserves a CEL envelope instead ofcollapsing it to a
${source}string, anduseConditionaccepts and forwardsthe envelope (keyed on a stable
(dialect, source)so it doesn't re-evaluateeach render). Action buttons (
action-icon/group/bar/button) thereforeevaluate CEL
visible/enabled/disabledon the canonical engine.Back-compat: bare strings and
${…}templates stay on the legacy JS path(deprecation window); only an explicit
{ dialect: 'cel' }envelope is rerouted.{ dialect: 'template' }is unaffected.Together with the
^15.1.1alignment (chore(deps): align @objectstack/formula|lint|client to ^15.1.1 (spec skew) #2662), a renderer CEL predicate nowreaches the identical verdict as the server — including the framework's
dateField == today()equality fix (feat(formula):dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) once itlands in a published 15.x. The broader home-grown-vs-canonical divergence
motivation is Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661.Patch Changes
@object-ui/console@16.1.0
Patch Changes
8b8b744: chore(deps): align
@objectstack/formula/lint/clientto^15.1.1These three were still pinned to
^14.6.0while@objectstack/specwas already^15.1.1— a version skew from the v15 upgrade (formula/lint/client publish inlockstep with spec, and their own 15.0.0 entries are pure dependency bumps, so
this is alignment, not a behavioral migration).
Practical effect: the client-side field-rule evaluation
(
visibleWhen/readonlyWhen/requiredWhenviafieldRules.ts, which delegatesto
@objectstack/formula'sExpressionEngine) now tracks the 15.x engine — andwill pick up the framework's
dateField == today()equality fix(feat(formula):
dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) automatically at the next 15.x release via thecaret range. Renderer/action
visible/disabledpredicates are unaffected (theyuse the home-grown JS evaluator — tracked separately in Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661).@object-ui/auth@16.1.0
Patch Changes
@object-ui/cli@16.1.0
Patch Changes
@object-ui/collaboration@16.1.0
Patch Changes
@object-ui/components@16.1.0
Patch Changes
@object-ui/data-objectstack@16.1.0
Patch Changes
8b8b744: chore(deps): align
@objectstack/formula/lint/clientto^15.1.1These three were still pinned to
^14.6.0while@objectstack/specwas already^15.1.1— a version skew from the v15 upgrade (formula/lint/client publish inlockstep with spec, and their own 15.0.0 entries are pure dependency bumps, so
this is alignment, not a behavioral migration).
Practical effect: the client-side field-rule evaluation
(
visibleWhen/readonlyWhen/requiredWhenviafieldRules.ts, which delegatesto
@objectstack/formula'sExpressionEngine) now tracks the 15.x engine — andwill pick up the framework's
dateField == today()equality fix(feat(formula):
dateField == today()now matches — AST temporal-comparison rewrite (#3183) framework#3205) automatically at the next 15.x release via thecaret range. Renderer/action
visible/disabledpredicates are unaffected (theyuse the home-grown JS evaluator — tracked separately in Renderer/action
visible/disabledpredicates bypass the canonical CEL engine — home-grown JS evaluator diverges from server enforcement #2661).Updated dependencies [8b8b744]
Updated dependencies [2e7d7f0]
@object-ui/fields@16.1.0
Patch Changes
@object-ui/layout@16.1.0
Patch Changes
@object-ui/mobile@16.1.0
Patch Changes
@object-ui/permissions@16.1.0
Patch Changes
@object-ui/plugin-ai@16.1.0
Patch Changes
@object-ui/plugin-calendar@16.1.0
Patch Changes
@object-ui/plugin-charts@16.1.0
Patch Changes
@object-ui/plugin-chatbot@16.1.0
Patch Changes
@object-ui/plugin-dashboard@16.1.0
Patch Changes
@object-ui/plugin-designer@16.1.0
Patch Changes
@object-ui/plugin-detail@16.1.0
Patch Changes
@object-ui/plugin-editor@16.1.0
Patch Changes
@object-ui/plugin-form@16.1.0
Patch Changes
@object-ui/plugin-gantt@16.1.0
Patch Changes
@object-ui/plugin-grid@16.1.0
Patch Changes
@object-ui/plugin-kanban@16.1.0
Patch Changes
@object-ui/plugin-map@16.1.0
Patch Changes
@object-ui/plugin-markdown@16.1.0
Patch Changes
@object-ui/plugin-report@16.1.0
Patch Changes
@object-ui/plugin-timeline@16.1.0
Patch Changes
@object-ui/plugin-tree@16.1.0
Patch Changes
@object-ui/plugin-view@16.1.0
Patch Changes
@object-ui/providers@16.1.0
Patch Changes
@object-ui/runner@16.1.0
Patch Changes
@object-ui/create-plugin@16.1.0
@object-ui/i18n@16.1.0
@object-ui/plugin-list@16.1.0
@object-ui/react-runtime@16.1.0
@object-ui/sdui-parser@16.1.0
@object-ui/types@16.1.0
object-ui@16.1.0
Patch Changes