Skip to content

docs(changeset): date the spec-symbol gate's export filter in the #6286 release note (objectui#9528) #10970

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
objectstack-fleet merged 1 commit into from
Sep 28, 2026
Merged

docs(changeset): date the spec-symbol gate's export filter in the #6286 release note (objectui#9528) #10970

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
5 changes: 3 additions & 2 deletions .changeset/6286-explain-batch-cap-from-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ cap and the spec follows, the client follows too, instead of paginating at the o
with no signal anywhere. The cap's whole point is that an over-cap request is refused with
`400 VALIDATION_FAILED` rather than truncated, so a client that silently disagrees with it
is exactly the drift `scripts/check-spec-symbol-derivation.mjs` argues about — and could
not catch here, because both of its scanners skip non-exported declarations and this const
was module-local (objectui#5899).
not catch here: when this change landed, both of its scanners skipped non-exported
declarations, and this const was module-local (objectui#5899). objectui#6291 has since
removed that filter from both scanners.

The declared floor already carries the symbol, so no range moves: `@objectstack/spec@17.0.0`
— the minimum `^17.0.0` admits — exports `EXPLAIN_BATCH_MAX_RECORD_IDS = 200` from
Expand Down
Loading