chore: version packages#1934
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 16, 2026 02:50
bb8b360 to
53d3ffc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 16, 2026 02:59
53d3ffc to
7ecb6a5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 16, 2026 03:23
7ecb6a5 to
5f37ae3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
June 16, 2026 03:32
5f37ae3 to
c6bd147
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/cli@9.7.0
Minor Changes
ff0a87a: feat(validate): flag bare field references in record-scoped CEL sites at build time
A
Field.formulaand an object validation predicate evaluate against therecordnamespace only — there is no field flattening — so a bare top-levelidentifier (
amount,status) resolves to nothing and the expression silentlyevaluates to
null/ never fires. This is the silent-at-runtime class behindthe broken example-crm formulas (fix(example-crm): make formula fields compute + allow historical closed deals; bump objectui #1927) and is exactly what AI authors get wrong.
validateExpressionnow takes an evaluationscopeand, forscope: 'record',reports a bare reference with the corrective form (
write record.<field>). Thecheck is schema-free and acts only on cel-js's
Unknown variablefault, so itcannot false-positive on arithmetic/comparison/null-guard type overloads. Flow
and automation conditions keep the default
scope: 'flattened'— the record'sfields ARE spread to top-level there (alongside flow variables), so bare refs
are correct and are NOT flagged.
objectstack compilewiresrecordscope forfield formulas and validation predicates; flow conditions stay flattened.
Patch Changes
417b6ac: feat(validate): advisory did-you-mean warnings for likely field typos in flow conditions
Adds a non-blocking warning channel to build-time expression validation (Formula guardrail: cel-js arithmetic silently returns null (double × int + bare identifiers) #1928
tier 3). Flow / automation conditions flatten the record's fields to top-level,
so a bare
statusis correct — but a bare NON-field identifier is either a flowvariable or a typo. When it is a near-miss of a known field (edit distance), the
build now emits a
did you mean \status`?warning instead of staying silent, WITHOUT failing the build (a genuine flow variable won't be close to a field name, so it stays quiet).ExprValidationResultgains awarningsarray andExprIssueaseverity;objectstack compile` prints warnings and only fails onerrors. This closes the silent-skip gap for misspelled trigger-condition fields
(the [P1] Flow trigger conditions with unknown functions are silently skipped (no error, passes build) #1877 family) without the false-positive risk of a hard gate.
Updated dependencies [82c7438]
Updated dependencies [417b6ac]
Updated dependencies [ff0a87a]
@objectstack/formula@9.7.0
Minor Changes
ff0a87a: feat(validate): flag bare field references in record-scoped CEL sites at build time
A
Field.formulaand an object validation predicate evaluate against therecordnamespace only — there is no field flattening — so a bare top-levelidentifier (
amount,status) resolves to nothing and the expression silentlyevaluates to
null/ never fires. This is the silent-at-runtime class behindthe broken example-crm formulas (fix(example-crm): make formula fields compute + allow historical closed deals; bump objectui #1927) and is exactly what AI authors get wrong.
validateExpressionnow takes an evaluationscopeand, forscope: 'record',reports a bare reference with the corrective form (
write record.<field>). Thecheck is schema-free and acts only on cel-js's
Unknown variablefault, so itcannot false-positive on arithmetic/comparison/null-guard type overloads. Flow
and automation conditions keep the default
scope: 'flattened'— the record'sfields ARE spread to top-level there (alongside flow variables), so bare refs
are correct and are NOT flagged.
objectstack compilewiresrecordscope forfield formulas and validation predicates; flow conditions stay flattened.
Patch Changes
82c7438: fix(formula): register mixed
double <op> intarithmetic overloads so number-field formulas computecel-js types a record field number as
doubleand a bare integer literal asint, and ships overloads only for matching numeric pairs. So an everydayformula like
record.amount / 100orrecord.price * 2faulted at runtime(
no such overload: dyn<double> / int); the engine caught the fault and theformula silently evaluated to
null— passing build, empty at runtime (Formula guardrail: cel-js arithmetic silently returns null (double × int + bare identifiers) #1928).The CEL engine now registers the missing
double <op> int/int <op> doubleoverloads for
+ - * / %, computing the result as adouble(CEL's mixed-numericpromotion). Pure
int op intis untouched, so integer division (7 / 2 == 3)keeps its semantics — the overloads fire only when the operands are genuinely a
doubleand anint. Authors no longer need the/ 100.0float-literal workaround.417b6ac: feat(validate): advisory did-you-mean warnings for likely field typos in flow conditions
Adds a non-blocking warning channel to build-time expression validation (Formula guardrail: cel-js arithmetic silently returns null (double × int + bare identifiers) #1928
tier 3). Flow / automation conditions flatten the record's fields to top-level,
so a bare
statusis correct — but a bare NON-field identifier is either a flowvariable or a typo. When it is a near-miss of a known field (edit distance), the
build now emits a
did you mean \status`?warning instead of staying silent, WITHOUT failing the build (a genuine flow variable won't be close to a field name, so it stays quiet).ExprValidationResultgains awarningsarray andExprIssueaseverity;objectstack compile` prints warnings and only fails onerrors. This closes the silent-skip gap for misspelled trigger-condition fields
(the [P1] Flow trigger conditions with unknown functions are silently skipped (no error, passes build) #1877 family) without the false-positive risk of a hard gate.
@objectstack/express@9.7.0
Patch Changes
@objectstack/fastify@9.7.0
Patch Changes
@objectstack/hono@9.7.0
Patch Changes
@objectstack/nestjs@9.7.0
Patch Changes
@objectstack/nextjs@9.7.0
Patch Changes
@objectstack/nuxt@9.7.0
Patch Changes
@objectstack/sveltekit@9.7.0
Patch Changes
@objectstack/account@9.7.0
Patch Changes
@objectstack/setup@9.7.0
Patch Changes
@objectstack/studio@9.7.0
Patch Changes
@objectstack/client@9.7.0
Patch Changes
@objectstack/client-react@9.7.0
Patch Changes
@objectstack/cloud-connection@9.7.0
Patch Changes
@objectstack/connector-mcp@9.7.0
Patch Changes
@objectstack/connector-openapi@9.7.0
Patch Changes
@objectstack/connector-rest@9.7.0
Patch Changes
@objectstack/connector-slack@9.7.0
Patch Changes
@objectstack/core@9.7.0
Patch Changes
@objectstack/mcp@9.7.0
Patch Changes
@objectstack/metadata@9.7.0
Patch Changes
@objectstack/metadata-core@9.7.0
Patch Changes
@objectstack/metadata-fs@9.7.0
Patch Changes
@objectstack/objectql@9.7.0
Patch Changes
@objectstack/observability@9.7.0
Patch Changes
@objectstack/platform-objects@9.7.0
Patch Changes
@objectstack/driver-memory@9.7.0
Patch Changes
@objectstack/driver-mongodb@9.7.0
Patch Changes
@objectstack/driver-sql@9.7.0
Patch Changes
@objectstack/driver-sqlite-wasm@9.7.0
Patch Changes
@objectstack/embedder-openai@9.7.0
Patch Changes
@objectstack/knowledge-memory@9.7.0
Patch Changes
@objectstack/knowledge-ragflow@9.7.0
Patch Changes
@objectstack/plugin-approvals@9.7.0
Patch Changes
@objectstack/plugin-audit@9.7.0
Patch Changes
@objectstack/plugin-auth@9.7.0
Patch Changes
@objectstack/plugin-dev@9.7.0
Patch Changes
@objectstack/plugin-email@9.7.0
Patch Changes
@objectstack/plugin-hono-server@9.7.0
Patch Changes
@objectstack/plugin-msw@9.7.0
Patch Changes
@objectstack/plugin-org-scoping@9.7.0
Patch Changes
@objectstack/plugin-reports@9.7.0
Patch Changes
@objectstack/plugin-security@9.7.0
Patch Changes
@objectstack/plugin-sharing@9.7.0
Patch Changes
@objectstack/plugin-webhooks@9.7.0
Patch Changes
@objectstack/rest@9.7.0
Patch Changes
@objectstack/runtime@9.7.0
Patch Changes
@objectstack/service-ai@9.7.0
Patch Changes
@objectstack/service-analytics@9.7.0
Patch Changes
@objectstack/service-automation@9.7.0
Patch Changes
@objectstack/service-cache@9.7.0
Patch Changes
@objectstack/service-cluster@9.7.0
Patch Changes
@objectstack/service-cluster-redis@9.7.0
Patch Changes
@objectstack/service-datasource@9.7.0
Patch Changes
@objectstack/service-feed@9.7.0
Patch Changes
@objectstack/service-i18n@9.7.0
Patch Changes
@objectstack/service-job@9.7.0
Patch Changes
@objectstack/service-knowledge@9.7.0
Patch Changes
@objectstack/service-messaging@9.7.0
Patch Changes
@objectstack/service-package@9.7.0
Patch Changes
@objectstack/service-queue@9.7.0
Patch Changes
@objectstack/service-realtime@9.7.0
Patch Changes
@objectstack/service-settings@9.7.0
Patch Changes
@objectstack/service-storage@9.7.0
Patch Changes
@objectstack/trigger-api@9.7.0
Patch Changes
@objectstack/trigger-record-change@9.7.0
Patch Changes
@objectstack/trigger-schedule@9.7.0
Patch Changes
@objectstack/types@9.7.0
Patch Changes
@objectstack/console@9.7.0
create-objectstack@9.7.0
@objectstack/spec@9.7.0
objectstack-vscode@9.7.0
@objectstack/example-crm@4.0.49
Patch Changes
@objectstack/example-showcase@0.1.19
Patch Changes
@example/app-todo@4.0.49
Patch Changes