This page gives a reproducible method, not a table of 'what an upgrade changes'. We have not finished the 0.2.2 comparison, so no specific entries are filled in — inventing them is worse than leaving the gap.
Upgrades touching config is not surprising; what hurts is being unable to say what it looked like before. Capture a baseline with the same command on the same machine, once before and once after.
Before
dsh --dump-config > before.yml
For the default layer only (no user layer), use --dump-default-config. Keeping both tells you whether the version changed or your own edits vanished.
Upgrade
npm i -g @deepseek-ai/[email protected]
Back up the profiles directory first, as on the previous page. An overwritten config is recoverable only if that backup exists.
After
dsh --dump-config > after.yml diff before.yml after.yml
The diff produces three kinds of result, each handled differently:
- Added entries: new keys. Defaults usually work, but read what they control.
- Removed entries: the alarming case. A rename, or a feature dropped — your setting may be silently dead.
- Changed values: default shifts. If your setup leaned on the old default, behaviour changes.
Turning this into material others can use
- State the version pair (verbatim
dsh --version), node version, and OS. - Paste the diff verbatim, not 'the config changed'.
- For each removed entry, say what you used it for and what replaces it — that is the part people need.