Skip to content

Commit ee14924

Browse files
committed
chore(changeset): patch for the stage-11 rationale and comment rewrite
The step rationales ship in @objectstack/spec's dist (dist/migrations/index.js and .mjs carry the new phrases, the old ones in 0 files, an unchanged control phrase in the same 2), so the release takes a patch note. Clause-②: no. Claude-Session: https://claude.ai/code/session_01YDt3PzwfrkuFzUBF89WPmM Co-authored-by: Claude <noreply@anthropic.com>
1 parent 005c541 commit ee14924

1 file changed

Lines changed: 19 additions & 0 deletions

File tree

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
'@objectstack/spec': patch
3+
---
4+
5+
Nine migration-step rationale passages state their decisions in words instead of tracker numbers, and two registry comments cite the commit that decided them
6+
7+
Clause-②: no
8+
9+
The protocol 17 and protocol 18 step rationales are what `os migrate meta` shows per hop
10+
and what the protocol upgrade guide prints. Nine of their passages named GitHub issues
11+
that no longer exist, so an upgrading author met a number with nothing behind it. Each of
12+
those passages now carries no number at all and says what was decided: why `mongo` and
13+
`mongodb` are both accepted, why the form-view option `default` and `connector.errorMapping`
14+
were retired, which earlier cleanup the import mapping `lookup` params finish, what the
15+
memory driver's placeholder refusal extends, how the plugin manifest's `contributes`
16+
members and `routes` were retired, and why the stack `themes` carrier and the
17+
component-translation `submitLabel` key went. Two source comments of the migration
18+
registry now cite the commit behind them. Text only: no migration step, entry, retired key
19+
or def, conversion, schema, export or runtime behaviour changes.

0 commit comments

Comments
 (0)