Skip to content

chore(changeset): bump bare-ref validation to minor + downstream note #1935

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 1 commit into from
Jun 16, 2026
Merged

chore(changeset): bump bare-ref validation to minor + downstream note #1935

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions .changeset/validate-formula-bare-refs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,18 @@
---
"@objectstack/formula": patch
"@objectstack/cli": patch
"@objectstack/formula": minor
"@objectstack/cli": minor
---

feat(validate): flag bare field references in record-scoped CEL sites at build time

> **Heads-up for downstream:** this adds a NEW build-time error. A `Field.formula`
> or validation predicate that references a field bare (`amount` instead of
> `record.amount`) now fails `objectstack compile`. These expressions were already
> silently broken at runtime (they evaluated to `null` / never fired), so this is a
> fix that surfaces a latent bug — but a stack carrying one will go from
> "builds, silently wrong" to "fails the build" on upgrade. The error message
> states the exact correction (`write record.<field>`).

A `Field.formula` and an object validation predicate evaluate against the
`record` namespace only — there is no field flattening — so a bare top-level
identifier (`amount`, `status`) resolves to nothing and the expression silently
Expand Down