Found by the docs sweep run 2 the tracker calls for (#3909 section D, watermark a641d10 → 2bafe62e8). Verified on main @ 1ee48bc60.
Nine passages across four hand-written docs state that the #4286 query-surface removals landed in @objectstack/spec 18. They landed in 17 — this train.
content/docs/protocol/objectql/query-syntax.mdx:726 query.distinct … removed in `@objectstack/spec` 18
content/docs/protocol/objectql/query-syntax.mdx:796 query.joins … 18
content/docs/protocol/objectql/query-syntax.mdx:808 query.windowFunctions … 18
content/docs/protocol/objectql/query-syntax.mdx:874 query.cursor … 18
content/docs/data-modeling/queries.mdx:259 query.cursor … 18
content/docs/data-modeling/queries.mdx:425 query.joins … 18
content/docs/data-modeling/queries.mdx:535 query.windowFunctions … 18
content/docs/data-modeling/queries.mdx:568 query.distinct … 18
content/docs/deployment/troubleshooting.mdx:283 cursor … 18
Everything the runtime says disagrees:
packages/spec/package.json → 17.0.0-rc.1
packages/spec/src/kernel/protocol-version.ts → PROTOCOL_VERSION = '17.0.0'
os migrate meta --from 16 → "[protocol 17] data.query.cursor → …"
"[protocol 17] data.query.distinct → …"
"[protocol 17] data.query.joins → …"
"[protocol 17] data.query.windowFunctions → …"
The #4286 changesets are in the rc.1 window and ship in 17.0.0.
Why it is worth fixing before RC exit
The number is the actionable part of these passages. A reader on 16 who needs to know whether upgrading to 17 breaks their cursor-paginated loop is told the removal is a major away — so they plan for it later and their upgrade breaks. It also contradicts the v17 release page, which correctly lists the same removals under 17, and the migration chain a reader would run.
Suggested fix: removed in \@objectstack/spec` 18→17` in the nine places above. Worth grepping for the bare pattern rather than fixing file by file, in case the same phrasing reached other passages the fingerprint list does not cover.
Logged as part of docs sweep run 2 for #3909; the sweep's own run-log entry (docs/v17-docs-sweep.md) should record this fingerprint so the next run checks the version number, not just the surface name.
Found by the docs sweep run 2 the tracker calls for (#3909 section D, watermark
a641d10→2bafe62e8). Verified onmain@1ee48bc60.Nine passages across four hand-written docs state that the
#4286query-surface removals landed in@objectstack/spec18. They landed in 17 — this train.Everything the runtime says disagrees:
The
#4286changesets are in the rc.1 window and ship in 17.0.0.Why it is worth fixing before RC exit
The number is the actionable part of these passages. A reader on 16 who needs to know whether upgrading to 17 breaks their
cursor-paginated loop is told the removal is a major away — so they plan for it later and their upgrade breaks. It also contradicts the v17 release page, which correctly lists the same removals under 17, and the migration chain a reader would run.Suggested fix:
removed in \@objectstack/spec` 18→17` in the nine places above. Worth grepping for the bare pattern rather than fixing file by file, in case the same phrasing reached other passages the fingerprint list does not cover.Logged as part of docs sweep run 2 for #3909; the sweep's own run-log entry (
docs/v17-docs-sweep.md) should record this fingerprint so the next run checks the version number, not just the surface name.