Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
31 changes: 31 additions & 0 deletions .changeset/6361-spec-floor-17-2-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
'@object-ui/core': patch
'@object-ui/data-objectstack': patch
---

`@object-ui/core` and `@object-ui/data-objectstack` now declare
`"@objectstack/spec": "^17.2.0"` rather than `^17.0.0`, which is the lowest published
spec that carries every symbol each package's own build output references
(objectui#6361).

`packages/core/dist/utils/column-sortability.d.ts` references
`FIELD_SORTABLE_UNPROVISIONED_ANCHOR`, `FIELD_UNSORTABLE_VIRTUAL_TYPE`,
`FieldSortability` and `ObjectSortability` from `@objectstack/spec/api`, and
`packages/data-objectstack/dist/index.js` references the first two — none of which
`@objectstack/spec@17.0.0` exports. Measured against the published tarballs rather than
the installed tree, by `scripts/check-spec-range-floors.mjs`: six `floor-too-low`
findings across the two packages, and `^17.2.0` is that gate's own computed answer for
both. So the old range was a claim neither package could honour: any consumer
resolution that lands 17.0.0 — a sibling pinning it exactly, an `overrides` entry, a
mirror two minors behind — satisfied `^17.0.0` and got a dangling reference.

Nothing a consumer installs today changes: normal resolution already picks the newest
17.x, and `pnpm-lock.yaml` still resolves `17.2.0` on both edges after the bump — only
the recorded `specifier:` moves. No source and no behaviour changes, which is why this
is scored `patch`, on the reasoning objectui#5793 used for the same remediation on
`@object-ui/plugin-detail`.

The bump is release-blocking rather than cosmetic. `check:spec-floors` is deliberately
not a `pull_request` job, so every PR stayed green while its blocking copy on the
publish path — `pnpm changeset:publish` runs it before a single tarball reaches npm —
would have cancelled the next release.
2 changes: 1 addition & 1 deletion packages/core/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@
"dependencies": {
"@object-ui/types": "workspace:*",
"@objectstack/formula": "^17.0.0",
"@objectstack/spec": "^17.0.0",
"@objectstack/spec": "^17.2.0",
"lodash": "^4.18.1",
"zod": "^4.4.3"
},
Expand Down
2 changes: 1 addition & 1 deletion packages/data-objectstack/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
"@object-ui/core": "workspace:*",
"@object-ui/types": "workspace:*",
"@objectstack/client": "^17.0.0",
"@objectstack/spec": "^17.0.0"
"@objectstack/spec": "^17.2.0"
},
"devDependencies": {
"tsup": "^8.5.1",
Expand Down
4 changes: 2 additions & 2 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading