[wp-trac] [WordPress Trac] #65368: Build/Test Tools: Bump bundled Gutenberg build to `0e198c7`
WordPress Trac
noreply at wordpress.org
Thu May 28 21:36:37 UTC 2026
#65368: Build/Test Tools: Bump bundled Gutenberg build to `0e198c7`
------------------------------+-----------------------------
Reporter: adamsilverstein | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: normal | Keywords:
Focuses: |
------------------------------+-----------------------------
Core bundles a pre-built copy of Gutenberg, pinned by commit SHA in the
custom `gutenberg.sha` field of `package.json`. This ticket bumps that pin
to `0e198c7ac7ca634e73ded9220ce048c0302174dd` and refreshes the
regenerated build artifacts.
The pin tracks the `wp/next` branch rather than Gutenberg `trunk`: trunk
currently requires React 19 while core ships React 18, so a trunk-based
bundle breaks the block editor. `0e198c7` is the current tip of `wp/next`,
is React-18 compatible, and carries the HEIC client-side code.
== Notes ==
* The changed files under `src/wp-includes/{blocks,assets,build,images}`
are regenerated Gutenberg build output, produced by `npm run
gutenberg:download`.
* `package.json`'s `gutenberg.sha` field is the only hand edit; `package-
lock.json` is unaffected, because the SHA lives in a custom field rather
than the npm dependency tree.
== Patch ==
* [https://github.com/WordPress/wordpress-develop/pull/12009 PR 12009] -
`update/bundled-gutenberg-0e198c7`
== Steps to reproduce / verify ==
1. Apply the patch (or check out [https://github.com/WordPress/wordpress-
develop/pull/12009 PR 12009]).
2. Run `npm run build` and confirm the block editor loads without React
initialization errors.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/65368>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list