馃悰(codemod) use published package ranges - #294
Merged
Merged
Conversation
jbpenrath
reviewed
Aug 6, 2026
Contributor
|
Don't forget to generate a changeset |
The dependency migration assigned ^1.0.0 to every replacement package, but ui-tokens keeps the Cunningham 3.1.0 version. This left migrated applications with a range that cannot resolve the published token release. Keep the default range next to each target package and cover both current and legacy package mappings in the transformation tests.
Record the major release that moves ui-components from 0.29.0 to the stable 1.0.0 line. ui-tokens remains on its published 3.1.0 version.
PanchoutNathan
force-pushed
the
fix/codemod-package-ranges
branch
from
August 6, 2026 11:05
3b6adb8 to
80cb924
Compare
jbpenrath
approved these changes
Aug 6, 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.
The dependency migration assigned ^1.0.0 to every replacement package, but ui-components is published as 0.29.0 and ui-tokens as 3.1.0. This left migrated applications with ranges that cannot resolve the available releases.
Keep the default range next to each target package and cover both current and legacy package mappings in the transformation tests.