-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency package @types/node-fetch has a new version available #19165
Comments
This task should be taken up along with #19231 |
Version 3.0.3 is deprecated we should stay in the 2.x.x range. @praveenkuttappan is there any way to have the automation tool to only check for new version in the 2.x.x range for this package? |
Automation is filing issue based on rush update output. We don't have control at package level. |
Once #19231 is addressed we need to remove this dependency. node-fetch already has types released with the package. See details in the linked issue about why we can't migrate at this time |
We have identified a dependency on version 2.5.0 of @types/node-fetch. A new version (2.6.4) is available for upgrade.
Following are the steps to upgrade package dependency.
Understand the breaking changes between the version being used and the version you want to upgrade to.
Identify all packages that take a dependency on this package.
Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.
Run rush update to ensure the new version is pulled in.
Make relevant changes to absorb the breaking changes.
Repeat steps 3 to 5 for each of the packages that have a dependency on this package.
The text was updated successfully, but these errors were encountered: