-
Notifications
You must be signed in to change notification settings - Fork 296
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
Chore: upgrade all package dependencies. #1356
Comments
IB ✅ |
After working on npm dependencies I stuck with a weird issue that blocked everything. I can't troubleshoot it too much because the error message is very vague and it looks like the issue happens inside of @wordpress/data package. I would be grateful if @tofumatt or anyone from the team can look at it too. The latest commint in my branch ( Here is the screenshot of the issue that I see in my browser: |
@felixarntz @aaemnnosttv @tofumatt i have prepared a few separate PRs to upgrade dependencies in chunks. Could you please review it and merge if possible? I need it to be merged to unblock another updates.
|
@eugene-manuilov I've approved and merged all 4 PRs. What's left here now? Would be great if you could provide an update, and then we can decide whether we're gonna invest the time or create separate follow-up issues for later. |
Here is a PR #1762 to upgrade all WordPress dependencies except @wordpress/data and @wordpress/script which can't be upgraded to the latest versions yet. It also includes a few additional changes to address deprecation warnings which have appeared after testing library upgrade. |
With #1762 merged, we can consider this one completed for now. I've opened #1769, #1770 and #1771 for the remaining updates, we don't need to get to those right away though, especially since figuring them out will likely require some more time investment. Overall, in the future let's approach dependency updates more granularly. We should also think about putting a regular routine in place where we update dependencies so that they don't get as outdated over time again. Maybe we should force the versions where we know updating causes breakage in |
Actually we'll still need to update PHP dependencies. |
QA 🆗 needsDue to the size of this issue and changes I'll review the remaining outdated packages; all other behavioral changes will be covered by general QA for release and other issues now (some things have already been caught and addressed before this).
Overall, nothing blocking here but a few issues should be created for handling the remaining upgrades that do not have one yet. @eugene-manuilov would you please create the remaining issues here (or link me to them if any of these are already covered and I just missed them? 😄 ) for packages that still need to be upgraded? |
Also I just noticed that Husky hooks are not working anymore when committing via an app and we should probably downgrade it to v3. See typicode/husky#639 |
|
@aaemnnosttv new issues are created. Please, let me know if you want me to add something to it. |
Thanks @eugene-manuilov I think we could use issues for upgrading QA ✅ |
Task Description
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation Brief
composer.json
andpackage.json
should be updated to their latest versions as long as doing so does not result in site breakages - in which case this needs to be discussed.composer.json
- runcomposer outdated
- gives a list of packages which have updates. Incrementally update versions. Checking for breakages.package.json
- runnpm outdated
- - gives a list of dependency packages which have updates. Incrementally update versions. Checking for breakages .QA Brief
Changelog entry
The text was updated successfully, but these errors were encountered: