Skip to content

Commit b926d1e

Browse files
committed
chore(changeset): metadata-core provenance anchors reach the published declaration files
Clause-②: no Claude-Session: https://claude.ai/code/session_01DDZNkDVwPQnevTFcYE47H3 Co-authored-by: Claude <noreply@anthropic.com>
1 parent fcee5ff commit b926d1e

1 file changed

Lines changed: 20 additions & 0 deletions

File tree

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
'@objectstack/metadata-core': patch
3+
---
4+
5+
Provenance comments in `@objectstack/metadata-core` cite the commits that decided them, not tracker numbers that no longer resolve
6+
7+
Clause-②: no
8+
9+
Docblocks and comments across the package cited issue-tracker numbers that now answer 404 on GitHub.
10+
Each now cites the commit in this repository's history that made the decision it describes, with two
11+
exceptions: two comments on `retiredFromLoadPath`'s jurisdiction (in `artifact-forward-conversion.ts`
12+
and its test) cite ADR-0087, which records that determination, and five comments that meant an
13+
objectui issue now spell it `objectui#6111`, as they already spelled `objectui#6110` beside it. One
14+
commit citation sits inside a maintainer ruling quoted in `record-organization.ts`: the number there
15+
became the bracketed editorial substitution `[commit 7901b2dd2]`, the commit that landed the ruling it
16+
names, and the rest of the quotation is unchanged. Some of these docblocks sit on exported members, so
17+
the reworded text appears in the published declaration files (`index.d.ts` / `index.d.cts`,
18+
`testing.d.ts` and a shared declaration chunk); the JavaScript output and its sourcemaps do not change.
19+
20+
Comment only: no export, type, error code, status, message text or runtime behaviour changes.

0 commit comments

Comments
 (0)