Update Bundled @wordpress/* monorepo

[matticbot]

This PR contains the following updates:

Package	Change	Age	Confidence
@wordpress/admin-ui (source)	1.11.0 → 1.12.0
@wordpress/dataviews (source)	14.0.0 → 14.1.0
@wordpress/icons (source)	12.1.0 → 12.2.0
@wordpress/interface (source)	9.28.0 → 9.29.0
@wordpress/ui (source)	0.10.0 → 0.11.0
@wordpress/ui (source)	^0.10.0 → ^0.11.0
@wordpress/views (source)	~1.10.0 → ~1.11.0

---

Release Notes

WordPress/gutenberg (@​wordpress/admin-ui)

v1.12.0

Compare Source

Enhancements

• Increase page header vertical padding. #​77152

WordPress/gutenberg (@​wordpress/dataviews)

v14.1.0

Compare Source

Enhancements

• DataForm: Add min/max date range validation support for date and datetime fields. #​77201
• DataForm: support isDisabled field property. #​77090
• DataViews, DataForm: Use --wpds-cursor-control for interactive cursor styling. #​77259
• DataViews/DataViewsPicker: simplify defaultLayouts property. #​77232
• DataForm: Show tooltip in edit button in panel layout. #​77024
• DataViewsPicker: Add onReset prop to support view reset functionality. #​77288

Bug Fixes

• DataForm: Fix disabled state for date(time) control. #​77138
• DataViews: Fix compact density clipping and remove top/bottom padding. #​77054
• DataForm: Remove text-transform from panel field labels. #​77196

Code Quality

• DataViewsPicker: Remove unnecessary ref callbacks in grid and table layouts. #​77179

WordPress/gutenberg (@​wordpress/icons)

v12.2.0

Compare Source

WordPress/gutenberg (@​wordpress/interface)

v9.29.0

Compare Source

WordPress/gutenberg (@​wordpress/ui)

v0.11.0

Compare Source

Breaking Changes

• Text: Apply margin: 0, removing user-agent margins when the component renders as block-level elements (for example p or h1–h6 via render prop) (#​76970).
• AlertDialog: Revise component API (#​76937):
  • AlertDialog.Root: moved intent prop to AlertDialog.Popup;
  • AlertDialog.Popup: moved onConfirm prop to AlertDialog.Root (now optional; supports async handlers, { close: false } to keep the dialog open, and { error: '...' } to display a built-in error message);
  • AlertDialog.Popup: removed loading prop (async flows are now handled internally via Promise-returning onConfirm);
  • AlertDialog.Popup: made children optional in favor of a new description prop, which describes the alert dialog semantically.

New Features

• Add Popover primitive (#​76438).

Bug Fixes

• Card.Title, EmptyState.Title, EmptyState.Description: Fix ref and props being lost when a custom render element is provided (#​77160).
• Tabs.List: Fix render prop being silently discarded (#​77160).
• Card: Set default foreground color on Card.Root so content and currentColor icons (for example the CollapsibleCard chevron) are themeable by default (#​77013).

Enhancements

• Dialog: Update Header layout to support multiple trailing elements alongside the title (#​77161, #​77334).
• Dialog: Use Text internally for Dialog.Title, adopting the heading-xl variant for consistent typography (#​77161).
• Dialog, AlertDialog, Tooltip, Select: Add container prop to Popup for custom portal targets (#​77163).
• Add defensive styles against global WordPress stylesheets like common.css and forms.css (#​76783).
• VisuallyHidden: Improve Storybook stories and documentation for the render prop composition pattern.

Internal

• Card: Remove redundant margin: 0 from Card.Title now that Text applies it by default (#​77187).
• Normalize render prop handling across components and document conventions in CONTRIBUTING.md (#​77160).
• AlertDialog: Rewrite internals to use Base UI's AlertDialog primitives directly instead of Dialog wrappers. Introduces an internal state machine for async confirm flows (#​76937).
• Field.Label, Fieldset.Legend, Field.Details: Refactor VisuallyHidden composition to preserve semantic HTML elements when visually hiding content.
• Badge: Use Text component for typography (#​77295).
• Notice.ActionLink: Use Text component for typography (#​77332).
• Update @base-ui/react from 1.3.0 to 1.4.0 (#​77308).

WordPress/gutenberg (@​wordpress/views)

v1.11.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 02:59 AM, on day 1 of the month ( * 0-2 1 * * ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the renovate/bundled-@wordpress-monorepo branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack renovate/bundled-@wordpress-monorepo

bin/jetpack-downloader test jetpack-mu-wpcom-plugin renovate/bundled-@wordpress-monorepo

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[jp-launch-control]

Code Coverage Summary

This 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. 🤷

Full summary · PHP report · JS report

[tbradsha]

@anomiex as I understand it, these should run monthly:

jetpack/.github/renovate.json5

Line 8 in e2bb1b6

schedule: [ '* 0-2 1 * *' ],

Why then did we get one two days after the other merged? Does a merge trigger a recheck? If so, how do we avoid a perpetual cycle of these being generated?

[tbradsha]

CI seems happy. Will defer to the other teams to verify no UI breakage.

[anomiex]

Why then did we get one two days after the other merged?

@simison checked the checkbox on the dashboard issue to instruct Renovate to create it, at about 10:48 UTC today. Which is a perfectly valid thing to do, although it'd be welcome for someone doing that to start work on the PR right away once it's created. 🙂

P.S. For any a11n reading this comment who isn't already aware, you can go to https://github.com/Automattic/jetpack/actions/workflows/renovate.yml to trigger a manual Renovate run instead of waiting for the scheduled run to create the requested PR. A link to that page is also at the end of the dashboard issue:

The bot runs every two hours, and may be monitored or triggered ahead of schedule here.

[tbradsha]

Ah, I missed that it was manually ticked. Mystery solved.

[matticbot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[simison]

Yes, we're actively working on admin-ui and ui packages so we want to keep merging bundled changes as frequent as possible.

We'll need to review the changes to admin-ui with Zap thoroughly before merging.

[simison]

Within this PR we can also remove the margin here:

jetpack/projects/plugins/jetpack/_inc/client/settings/style.scss

Lines 116 to 123 in 8c976ec

	// @wordpress/ui zeros margins on EmptyState.Title/Description inside
	// @layer wp-ui-components, but unlayered admin styles (core + Jetpack)
	// take precedence and reintroduce h2/p margins. Reset them here so the
	// component renders with its intended tight spacing.
	h2,
	p {
	margin: 0;
	}