chore(migrate): target v9 by major instead of a dev build pin - #31359
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
brandyscarney
approved these changes
Aug 14, 2026
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.
Issue number: internal
What is the current behavior?
Currently,
@ionic/migratepins the@ionic/*packages to a specificmajor-9.0dev build, because v9 isn't published underlatestyet so^9.0.0wouldn't resolve. That pin is versioned8.8.x-dev, so semver reads it as major 8, and two pieces of code exist only to work around that.What is the new behavior?
In preparation for v9 to ship, the three dependency migrations target the major directly, matching how they already express
['react-router', 6]and['vue-router', 5]. That resolves to^9.0.0, so apps pick up v9 patch and minor releases without another migration run. TheIONIC_V9_VERSIONconstant andsrc/versions.tsare removed along with both workarounds, so nothing in the tool compares exact versions anymore, only majors and floors. Thevuebump keeps its range form because it's a 3.4 to 3.5 minor floor rather than a major.Does this introduce a breaking change?
Other information
This is the
TODO(FW-7579)swap that was always planned for GA.