feat(replacements): framer-motion to motion #32844
Conversation
|
|
| "matchDatasources": ["npm"], | ||
| "matchPackageNames": ["framer-motion"], | ||
| "replacementName": "motion", | ||
| "replacementVersion": "11.11.12" |
There was a problem hiding this comment.
This is not ideal because it could result in a rollback of versions.
I think that while @mattgperry is releasing both packages in parallel, maybe Renovate shouldn't proactively replace framer-motion with motion. If/once framer-motion is stopped then we no longer have a moving target for the replacement
There was a problem hiding this comment.
I think we should support replace name only. so we can simply leave the replacement version undefined and retain the current version for such use cases
There was a problem hiding this comment.
OK so requires a modification to the replacement logic to accept empty replacement version?
There was a problem hiding this comment.
I think so. @zharinov do you know?
|
Blocked by #33033 |
Changes
Created a replacement rule for
framer-motionwith its continuation packagemotion.Context
The package has been published as
motionsince version 11.11.12 following the merger between Framer Motion and Motion One.Proof:
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: