docs(migration): replace stale v2-to-v3 guide with v3-to-v5 - #16
Merged
Conversation
The old guide documented the 2.x whitelist change and was two major versions behind. The new guide covers the v5 upgrade path: Node 20 requirement, what carries over (config, history, 2025-era clients), the watch CLI replacement, content tool removal, and how to stay on 3.4.2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MIGRATION.md was still the v2.x whitelist guide, two major versions behind. This replaces it with the actual v5 upgrade path: Node 20 requirement, what carries over untouched (config.json, history, 2025-era MCP clients), recreating watches with the standalone CLI, the organize_smart/organize_by_content removal, and pinning 3.4.2 for anyone who needs the old tools. Markdownlint clean.