-
Notifications
You must be signed in to change notification settings - Fork 831
Update @wordpress/dataviews
from v7 to v9
#45213
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
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! |
Code Coverage SummaryThis PR did not change code coverage! That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷 |
7cc04f8
to
ae99ceb
Compare
Instead of doing this manually, you can check the appropriate checkbox in #23363 to ensure that the dependency is updated everywhere. Then you can make the edits/fixes in the PR created by the renovate bot. |
@manzoorwanijk thanks! Yep I'm aware we have the Renovate bot flows, but recently I've been ahead of these updates by spinning up PRs before the stable release. I do this when we have product needs for the update from Forms, like this time with empty states or last time with improved mobile UX. Otherwise, automated flows are fine. That said, I see nobody updated v8 meanwhile. |
ae99ceb
to
799e4a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Locally getting built failure for Forms package at least:
Click to expand
|
|
To fix the build error, simply make this change and run diff --git a/.pnpmfile.cjs b/.pnpmfile.cjs
index d4e605af23..83135ccf8d 100644
--- a/.pnpmfile.cjs
+++ b/.pnpmfile.cjs
@@ -16,6 +16,7 @@ const wpPkgs = {
'highlight-words-core',
'is-plain-object',
'memize',
+ 'react-colorful',
'@use-gesture/react',
'uuid',
'@wordpress/date', |
799e4a4
to
2046b57
Compare
Tested Forms works well. |
2046b57
to
8f76176
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Tests well on My Jetpack and Forms. The other projects do not seem to actually use the package.
Update
@wordpress/dataviews
from v7 to v9.See changelog for v8 and v9
Updates Forms to account for one breaking change:
empty
elements are no longer wrapped in<p>
tags to improve accessibility WordPress/gutenberg#71561Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: