Skip to content

docs: warn stable users about unsafe config migration - #7118

Open
Burakodbs wants to merge 3 commits into
code-yeongyu:devfrom
Burakodbs:docs/stable-config-migration-warning
Open

docs: warn stable users about unsafe config migration#7118
Burakodbs wants to merge 3 commits into
code-yeongyu:devfrom
Burakodbs:docs/stable-config-migration-warning

Conversation

@Burakodbs

@Burakodbs Burakodbs commented Aug 21, 2026

Copy link
Copy Markdown

Summary

  • warn stable 4.19.4 users that the reasoning-unification migration can produce a configuration rejected by that release
  • document the safe workaround while npm latest remains affected

Changes

  • add a version-specific warning to the configuration migration reference
  • explain that even --dry-run can resume a pending migration journal before dry-run handling
  • cover automatic migration triggers during startup and install
  • add a Known Issues entry with symptoms, backup guidance, workaround, and fix status

QA & Evidence

Risks & Residuals

  • Documentation-only change; no runtime behavior is modified.
  • Full project checks were not run locally because bun install --frozen-lockfile exhausted the temporary filesystem while its prepare hook fetched unrelated frontend submodules. Temporary install artifacts were removed afterward.

Automated Checks

git diff --check

Related Issues

Related to #6644.
Validation support: #6602.
Runtime follow-up: #6668.

@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

All contributors have signed the CLA. Thank you! ✅
Posted by the CLA Assistant Lite bot.

@Burakodbs

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

github-actions Bot added a commit that referenced this pull request Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant