feat(cli): map v2 commands and v2 state to v3 guidance - #138
Merged
Merged
Conversation
v2 users upgrading to v3 hit bare "unrecognized subcommand" errors and a lockfile "not valid JSON" error with no migration path.
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. Review completed. No material findings. |
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
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.
❓ Type of change
📚 Description
Stable v3 moves npm
latestoff 2.3.0, so every v2 user lands on the native CLI. Their muscle memory currently gets this:login,logout,whoami,info, andpreparenow run their v3 replacement. The removed commands (author,watch,cache, and the rest) exit withREMOVED_COMMANDand link the migration guide. A v2 YAML lockfile says to back up.skills, andskilld add vuepoints toskilld search vue.Not sure
prepare→installis right. A v2 project still fails there, but on the lockfile message, which is at least actionable.