Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: +507 B (+0.01%) Total Size: 8.75 MB
ℹ️ View Unchanged
|
|
Flaky tests detected in 44685bc. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/23217597565
|
What?
Updates
@base-ui/reactfrom 1.2.0 to 1.3.0 in@wordpress/ui.Why?
v1.3.0 (Mar 12, 2026) includes bug fixes for components we use (Autocomplete, Combobox, Select, Tabs, Tooltip, Field, ScrollArea, among others).
How?
DEFAULT_RENDERconstant todefaultRenderin Field, and theRenderinner function totextareaRenderin Textarea. Base UI 1.3 now warns when therenderprop receives a function whose name starts with an uppercase letter, interpreting it as a mistakenly passed component. This is a workaround — an upstream issue has been filed since the warning doesn't apply to our usage (we're passing render functions, not components).getAnimationspolyfill to global test mocks. Base UI's ScrollArea now callsElement.getAnimations(), which jsdom doesn't implement.Testing Instructions
TypeScript, build, and unit tests pass.
Use of AI Tools
Cursor was used for initial research and drafting.