Add an upgrade guide for moving from 1.x to 2.x - #62
Merged
Conversation
WendellAdriel
marked this pull request as ready for review
July 24, 2026 10:56
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
2 participants
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.
Overview
With 2.x becoming the active series, 1.x users have no documented path forward — and since 2.x is a rewrite, a few commands and behaviors changed along the way.
Solution
Adds an
UPGRADE.mdcovering the move: the 1.x series is frozen and no longer supported, how to update the global installation (PHP 8.3 and re-requiring past the^1.0constraint), the automatic~/.cpxcache migration, and each command or behavior change with its replacement. The README now links to the guide right after the intro so upgraders find it early.