Skip to content

Commit ac68eff

Browse files
committed
docs(spec): fill in the correcting PR number in the erratum line
The erratum line was written before PR #18077 existed; replace the placeholder with its real number now that it does.
1 parent bfc744c commit ac68eff

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

packages/spec/CHANGELOG.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2880,7 +2880,7 @@
28802880
*Erratum, 2026-09-13 — #17783 and #17785 renamed the two keys this entry
28812881
named as gate-exempt; both are tombstoned and inside the gate's
28822882
population as of `@objectstack/spec` 17. (Corrected after publication,
2883-
#PRPLACEHOLDER18076.)*
2883+
#18077.)*
28842884
- fb77aa5: feat(spec)!: a `tree` field's `reference`, when present, must name the declaring object — any other target is refused at parse (#14892)
28852885

28862886
<!-- adr-0087: not-required (no-migration-prescription) No authorable key is renamed, retired or re-typed: `reference` keeps its name, its type and its optionality on a `tree` field, and every self-referencing or reference-less `tree` parses byte-identically to before. What is newly refused is a `tree` whose `reference` names a different object — a shape no prose surface ever documented, that no runtime reader consumed as a cross-object link, and whose one in-repo author (the showcase field zoo) hedged in its own label. The remedy is authoring intent, not a mechanical rewrite: the author decides whether the field is this object's own hierarchy (a self-reference, or no `reference` at all) or a link to another object (a `lookup`), so `objectstack migrate meta` has nothing to rewrite and this changeset carries no rewrite instructions. -->

0 commit comments

Comments
 (0)