What’s new in Gutenberg 22.9? (8 April)
🔗 **Source:** [What’s new in Gutenberg 22.9? (8 April)](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/)
> [!note]+ Document Notes
> ---
> tags: #gutenberg #block-editor #wordpress-core #background-gradients #command-palette #collaboration
> author: Miguel Fonseca
> source: Make WordPress Core
> reference: https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/
> date created: 2024-12-27 14:30
> ---
> # 🏷️ Title: What's new in Gutenberg 22.9? (8 April)
> ## 🧰 Action Inbox
> - [H1] Implement background gradient support in Group blocks — new block support available for themes #gutenberg
> - [H2] Enable command palette experimental features — workflow palette in Gutenberg experiments #block-editor
> - [H3] Update collaboration workflows — improved multi-user editing stability #collaboration
> ## 🧭 Table of Contents
> - [[#📝 Summary]]
> - [[#📖 Main Content]]
> - [[#🗒️ Notes]]
> - [[#📚 References]]
> - [[#🗣️ Paraphrase]]
> - [[#📰 Newsletter]]
> - [[#✅ Action Items]]
> - [[#🧪 Hypotheses]]
> - [[#📊 Methodology]]
> - [[#❓ Questions]]
> - [[#🔮 Future Research]]
> - [[#💡 Implications]]
> - [[#🧠 Learning Styles Assessment]]
> - [[#📊 Accessibility Assessment]]
> - [[#🌍 DEIB Assessment]]
> - [[#✅ Logical Validity]]
> - [[#🛡️ DARVO Analysis]]
> - [[#🎯 Conclusion]]
> ### 🔗 References
> - [Gutenberg Release](https://github.com/WordPress/gutenberg/releases/tag/v22.9)
> - [WordPress Core Development](https://make.wordpress.org/core/)
> ## 📝 Summary
> - Gutenberg 22.9 introduces background gradients for Group blocks and experimental command palette improvements
> - Why it matters: Enhanced design capabilities and improved developer experience for block creation
> - Key stakeholders: Theme developers, site builders, plugin authors using block supports
> - Risks and tradeoffs: Experimental features require opt-in, potential migration needed for color.gradient usage
> - Bottom line: Significant UX improvements for editors with 131 merged PRs and 5 first-time contributors
> ## 📖 Main Content
> Gutenberg 22.9 delivers three major feature areas: background styling enhancements, command palette organization, and collaboration stability improvements. The release introduces a new background.gradient block support that allows gradients and background images to work together in Group blocks without conflicts. This addresses a long-standing limitation where background effects couldn't be combined effectively.
> The experimental command palette now features organized sections including "Recent commands" and "Suggestions" based on context, replacing the simple search interface. Users must enable "Workflow Palette" in Gutenberg experiments to access this feature.
> Real-time collaboration receives stability fixes for multi-user editing, including proper sync of block comments between editors and improved error recovery to prevent memory issues during collaborative sessions. The wordpress/ui package gains a new EmptyState component for consistent placeholder content across interfaces.
> ## 🗒️ Notes
> #### ⏱️ [MISSING] — [H1] Background gradients alongside background images
> - Key idea: Group block now supports background gradients through new background.gradient block support
> - Evidence: "allowing gradients and background images to work together without conflicts"
> #### ⏱️ [MISSING] — [H2] Command palette history and suggestions (experimental)
> - Key idea: Command palette features organized sections for Recent commands and Suggestions
> - Evidence: "Instead of showing just a search field and search results, users see sections for Recent commands and Suggestions based on current context"
> #### ⏱️ [MISSING] — [H3] EmptyState component addition
> - Key idea: wordpress/ui package adds EmptyState component for placeholder content
> - Evidence: "provides flexible composition with sub-components for icons, titles, descriptions, and actions"
> #### ⏱️ [MISSING] — [H2] Real-time collaboration improvements
> - Key idea: Block comments now properly sync between collaborative editors
> - Evidence: "Block comments (notes) now properly sync between collaborative editors instead of requiring page refreshes to appear"
> #### ⏱️ [MISSING] — [H3] Hidden input fields for Forms block
> - Key idea: Experimental Forms block supports hidden input fields as selectable placeholders
> - Evidence: "Hidden fields appear as selectable placeholder blocks in the editor, while remaining invisible on the frontend"
> #### ⏱️ [MISSING] — [H1] Block support architecture improvements
> - Key idea: New background.gradient support lays groundwork for migrating color.gradient across all blocks
> - Evidence: "eventually migrating color.gradient to background.gradient across all blocks, providing a more consistent and capable background styling system"
> #### ⏱️ [MISSING] — [H2] Collaboration lock management
> - Key idea: Post list action button correctly updates from "Join" to "Edit" when collaboration locks expire
> - Evidence: "action button correctly updates from 'Join' back to 'Edit' when collaboration locks expire"
> #### ⏱️ [MISSING] — [H3] Error recovery enhancements
> - Key idea: Enhanced error recovery prevents cascading failures during collaborative sessions
> - Evidence: "error recovery has been enhanced to prevent cascading failures that could previously cause memory issues"
> #### ⏱️ [MISSING] — [H2] Component improvements across packages
> - Key idea: Multiple component enhancements including DOM API preferences and UI typography updates
> - Evidence: "Prefer standard caretPositionFromPoint over deprecated caretRangeFromPoint"
> #### ⏱️ [MISSING] — [H1] Release statistics and community contribution
> - Key idea: 131 PRs merged with 5 first-time contributors from global development community
> - Evidence: "A total of 131 PRs were merged in Gutenberg 22.9, with 5 first-time contributors"
> ## 📚 References
> - [Gutenberg Project](https://wordpress.org/gutenberg/)
> - [Block Editor Handbook](https://developer.wordpress.org/block-editor/)
> - [Make WordPress Core](https://make.wordpress.org/core/)
> ## 🗣️ Paraphrase
> - Gutenberg 22.9 enables combining background gradients with images in Group blocks through a new block support system
> - The command palette receives experimental organizational improvements with recent commands and contextual suggestions sections
> - Real-time collaboration becomes more stable with proper block comment syncing and enhanced error recovery mechanisms
> ## 📰 Newsletter
> 🎨 **Design Freedom Unlocked**: Gutenberg 22.9 brings background gradients to Group blocks! Now you can layer beautiful gradients over background images without the technical headaches. Perfect for creating those eye-catching hero sections and rich design layouts.
> 🛠️ **Developer Benefits**: The new background.gradient block support opens doors for theme developers to create more sophisticated styling options. Plus, with 5 first-time contributors joining the project, the WordPress community continues growing stronger.
> **Try It Today**: Download Gutenberg 22.9 and experiment with gradient overlays. Don't forget to enable "Workflow Palette" in experiments for the improved command palette experience.
> Resources: [Learn WordPress](https://learn.wordpress.org/), [Block Editor Handbook](https://developer.wordpress.org/block-editor/), [Gutenberg GitHub](https://github.com/WordPress/gutenberg)
> ## ✅ Action Items
> #### WordPress
> - Core: Test background.gradient block support compatibility with existing themes
> - Core: Evaluate migration path from color.gradient to background.gradient
> - Core Program Team: Coordinate experimental features feedback collection
> - Community: Update documentation for new block supports in developer resources
> - Design: Create examples showcasing gradient+image combinations for design library
> - Documentation: Update Block Editor Handbook with background.gradient examples
> #### OSPO
> - Community Engagement: Recognize and support first-time contributors joining core development
> - Developer Support: Create tutorials for new block support implementations
> ## 🧪 Hypotheses
> - Background gradient support will increase adoption of Group blocks for complex layouts
> - Command palette improvements will reduce time spent searching for editor actions
> - Collaboration stability fixes will encourage more multi-user editing workflows
> - EmptyState component standardization will improve UI consistency across WordPress admin
> ### 📊 Methodology
> - Monitor Group block usage analytics before/after gradient support release
> - Track command palette usage patterns with experimental features enabled
> - Measure collaboration session stability and user satisfaction metrics
> - Survey theme developers on block support implementation adoption
> ### ❓ Questions
> - How will background.gradient migration affect existing color.gradient implementations?
> - What performance impact do combined gradients and images have on page load?
> - When will experimental command palette features graduate to stable release?
> ### 🔮 Future Research
> - Comprehensive block support system architecture for advanced styling
> - Real-time collaboration scaling for larger editing teams
> - Integration patterns for EmptyState component across WordPress ecosystem
> ### 💡 Implications
> - Practice: Theme developers gain more sophisticated background styling options
> - Policy: Experimental feature graduation criteria needs clear documentation
> - Education: Block support tutorials require updates for new gradient capabilities
> - Security: Multi-user collaboration improvements reduce data loss risks
> ### 🧠 Learning Styles Assessment
> Reading level estimate: 12th Grade (technical documentation)
> #### 👀 Visual learners
> - Present: Feature descriptions with block examples
> - Improve: Screenshots of gradient+image combinations, command palette sections
> #### 🔊 Aural learners
> - Present: Release announcement format
> - Improve: Video walkthrough of new features
> #### 🗣️ Verbal learners
> - Present: Clear feature explanations and technical terms
> - Improve: Glossary of block support terminology
> #### 🧩 Kinesthetic learners
> - Present: Download links and experimental feature toggles
> - Improve: Step-by-step implementation guides
> #### 🧠 Logical learners
> - Present: Organized changelog with categories
> - Improve: Feature dependency diagrams
> #### 🧑🤝🧑 Social learners
> - Present: Contributor recognition and community stats
> - Improve: Discussion forums for feature feedback
> #### 🧘♀️ Solitary learners
> - Present: Detailed technical specifications
> - Improve: Self-paced feature exploration guides
> #### 🌿 Naturalistic learners
> - Present: Evolutionary approach to block support system
> - Improve: Ecosystem impact discussions
> ### 📊 Accessibility Assessment
> #### Screen reader semantics
> - Present: Proper heading structure in changelog
> - Improve: ARIA labels for experimental features
> #### Keyboard navigation
> - Present: Command palette keyboard shortcuts maintained
> - Improve: Gradient picker keyboard accessibility
> #### Contrast and readability
> - Present: Standard WordPress admin contrast ratios
> - Improve: High contrast mode support for new components
> #### Text resizing and reflow
> - Present: Responsive design maintained
> - Improve: EmptyState component text scaling
> #### Media and captions
> - Present: Text-based feature descriptions
> - Improve: Alt text for feature screenshots
> #### Forms and interactions
> - Present: Accessible form controls mentioned
> - Improve: Hidden field accessibility documentation
> #### Standards reference
> - Map component improvements to WCAG 2.2 AA success criteria
> ### 🌍 DEIB Assessment
> #### Cultural breadth
> - Present: Global contributor recognition
> - Improve: Multi-language gradient support examples
> #### Inclusive language
> - Present: Technical terminology clearly defined
> - Improve: Avoid development-specific jargon in user features
> #### Neurodiversity support
> - Present: Organized information structure
> - Improve: Clear visual hierarchy in feature lists
> #### Representation
> - Present: Diverse contributor names and backgrounds
> - Improve: Inclusive example content in documentation
> #### Psychological safety
> - Present: Welcoming first-time contributor recognition
> - Improve: Clear contribution guidelines
> ### ✅ Logical Validity
> #### Strong reasoning
> - Deductive strength: Feature benefits logically follow from technical implementations
> - Inductive strength: Past release patterns support continued development trajectory
> - Causal reasoning: Clear connection between user needs and feature additions
> - Analogical strength: Block support system analogies help explain technical concepts
> #### Fallacies
> - Appeal to novelty: Some emphasis on "new" without sufficient benefit explanation
> - Bandwagon effect: Community participation numbers used as quality indicator
> #### Tone of voice
> - Overall tone: Professional, informative, developer-focused with appropriate technical detail
> ### 🛡️ DARVO Analysis
> - Deny: No denials present in technical release notes
> - Attack: No attacks on users or competitors
> - Reverse victim/offender: Not applicable to feature announcement
> - Emotional cues and rhetoric: Positive, collaborative language emphasizing community contribution
> ## 🎯 Conclusion
> Gutenberg 22.9 represents significant progress in WordPress block editor capabilities, particularly for designers seeking advanced background styling options and developers building collaborative editing experiences. The combination of gradient support, improved command palette organization, and collaboration stability fixes demonstrates continued commitment to both user experience and developer experience improvements.
> Practitioners should evaluate the new background.gradient block support for theme development opportunities while monitoring experimental features for future stable releases. The strong community contribution (5 first-time contributors) indicates healthy project growth and diverse development perspectives.
> ## 🧱 Refactor Appendix
> ### 📚 Literature Split Pad
> Purpose: Stage CEE units that become Literature notes.
> Split level: H3
> ### [H1] Background gradients work alongside background images in Group blocks
> > [!quote] [What's new in Gutenberg 22.9?](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/) by [[Miguel Fonseca]] via [[Make WordPress Core]]. Published 2026-04-09. Accessed 2024-12-27.
> > "The Group block now supports background gradients through a new background.gradient block support, allowing gradients and background images to work together without conflicts."
> Enables sophisticated design combinations previously impossible due to styling conflicts between gradient and image backgrounds.
> [view highlight](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/#H1) #xref #articleseed ID:rw_[MISSING]
> ### [H2] Command palette gains organized sections for better action discovery
> > [!quote] [What's new in Gutenberg 22.9?](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/)
> > "Instead of showing just a search field and search results, users see sections for Recent commands and Suggestions based on current context."
> Experimental feature requires enabling "Workflow Palette" in Gutenberg experiments section.
> [view highlight](https://make.wordpress.org/core/2026/04/09/whats-new-in-gutenberg-22-9-8-april/#H2) #xref ID:rw_[MISSING]
> ---
> ### 🔖 Atomic Split Pad (Zettel Candidates)
> Purpose: Promote reusable claims into Atomic notes.
> Split level: H4
> #### [Z1] Block support systems enable consistent styling APIs
> - Scope: WordPress block development architecture
> - Pointer: background.gradient block support introduction
> - Links: [[Block-Development]] [[WordPress-Architecture]]
> #### [Z2] Real-time collaboration requires robust error handling
> - Scope: Multi-user editing systems
> - Pointer: Collaboration stability improvements section
> - Links: [[Collaborative-Editing]] [[Error-Recovery]]
> ---
> ### ✏️ Fleeting Queue
> Purpose: Capture quick actions for Fleeting notes.
> - [F1] Test new gradient picker in Group blocks — background panel location #fleeting #inbox
> - [F2] Enable workflow palette experiment — Gutenberg settings evaluation #fleeting #inbox
> - [F3] Document EmptyState component usage — wordpress/ui package integration #fleeting #inbox
“What’s new in Gutenberg…” posts (labeled with the [#gutenberg-new tag](https://make.wordpress.org/core/tag/gutenberg-new/)) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, [here’s an overview](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) of different ways to keep up with Gutenberg and the Editor.
Gutenberg 22.9 has been released and is [available for download](https://wordpress.org/plugins/gutenberg/)!
This release introduces background gradients that work alongside background images in the Group block, and adds organized sections to the command palette for better action discovery (experimental). The wordpress/ui package gains a foundational component for consistent empty states, while real-time collaboration receives stability improvements for multi-user editing sessions.
A total of [131 PRs](https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+milestone%3A%22Gutenberg+22.9%22+is%3Aclosed+) were merged in Gutenberg 22.9, with 5 first-time contributors!
**Table of contents**
#### Background gradients alongside background images
[](https://make.wordpress.org/core/files/2026/04/image-3.png)
The Group block now supports background gradients through a new `background.gradient` block support, allowing gradients and background images to work together without conflicts. You’ll find a gradient picker in the Background panel that works independently of the existing color gradient controls, making it possible to create gradient overlays on images or combine multiple background effects.
The new `background.gradient` block support is available to block authors. This also lays the groundwork for eventually migrating `color.gradient` to `background.gradient` across all blocks, providing a more consistent and capable background styling system, including clipping and text gradients. ([75859](https://github.com/WordPress/gutenberg/pull/75859))
#### Command palette history and suggestions (experimental)
[](https://make.wordpress.org/core/files/2026/04/image-2.png)
The command palette (Cmd+K/Ctrl+K) now features organized sections that make it easier to find and reuse actions. Instead of showing just a search field and search results, users see sections for Recent commands and Suggestions based on current context. This change is experimental; to give it a try, first go to *WP-Admin* > *Gutenberg* > *Experiments* and enable “Workflow Palette”.
#### Other Notable Highlights
The wordpress/ui package adds a new EmptyState component for displaying placeholder content when sections have no data. This compound component provides flexible composition with sub-components for icons, titles, descriptions, and actions, laying groundwork for consistent empty state patterns across the interface ([74719](https://github.com/WordPress/gutenberg/pull/74719)).
[](https://make.wordpress.org/core/files/2026/04/image-1.png)
Real-time collaboration has received some fixes that improve the multi-user editing experience and stability. Block comments (notes) now properly sync between collaborative editors instead of requiring page refreshes to appear. In the post list, the action button correctly updates from “Join” back to “Edit” when collaboration locks expire. Behind the scenes, error recovery has been enhanced to prevent cascading failures that could previously cause memory issues during collaborative sessions. ([76873](https://github.com/WordPress/gutenberg/pull/76873), [76795](https://github.com/WordPress/gutenberg/pull/76795), [76872](https://github.com/WordPress/gutenberg/pull/76872), [76716](https://github.com/WordPress/gutenberg/pull/76716))
The experimental Forms block now supports hidden input fields, filling an important gap for many applications. Hidden fields appear as selectable placeholder blocks in the editor, while remaining invisible on the frontend with values configurable through the Advanced panel. ([74131](https://github.com/WordPress/gutenberg/pull/74131))
#### Changelog
###### Block Editor
* Add EmptyState component to wordpress/ui. ([74719](https://github.com/WordPress/gutenberg/pull/74719))
* Button: hide focus outline on :Active for click feedback in forced-colors mode. ([76833](https://github.com/WordPress/gutenberg/pull/76833))
* Card: Use Text component for Title typography. ([76642](https://github.com/WordPress/gutenberg/pull/76642))
* InputControl: Add to wordpress/ui. ([76653](https://github.com/WordPress/gutenberg/pull/76653))
* Snackbar: Use surface-width design token for max-width. ([76592](https://github.com/WordPress/gutenberg/pull/76592))
* Storybook: Make “introduction” top level. ([76671](https://github.com/WordPress/gutenberg/pull/76671))
* Tabs: Add runtime validation for tab/panel mismatches. ([75170](https://github.com/WordPress/gutenberg/pull/75170))
* Theme: Change default control cursor to pointer. ([76762](https://github.com/WordPress/gutenberg/pull/76762))
* ThemeProvider: Add cursor prop. ([76410](https://github.com/WordPress/gutenberg/pull/76410))
* UI/Dialog: Deprioritize close icon for initial focus. ([76910](https://github.com/WordPress/gutenberg/pull/76910))
* UI/Dialog: Expose initialFocus and finalFocus on Dialog.Popup. ([76860](https://github.com/WordPress/gutenberg/pull/76860))
* UI: Add AlertDialog primitive. ([76847](https://github.com/WordPress/gutenberg/pull/76847))
* Block Supports: Add background gradient support that can combine with background images. ([75859](https://github.com/WordPress/gutenberg/pull/75859))
* Forms Block: Add hidden input field variation. ([74131](https://github.com/WordPress/gutenberg/pull/74131))
* Image/Site Logo: Hide crop toolbar when editMediaEntity is unavailable. ([76626](https://github.com/WordPress/gutenberg/pull/76626))
* Login/out block: Add button block class names to the submit button. ([76746](https://github.com/WordPress/gutenberg/pull/76746))
* Site Editor > Pages: Move view configuration to the server. ([76573](https://github.com/WordPress/gutenberg/pull/76573))
* Site Editor > Patterns: Move configuration to the server. ([76734](https://github.com/WordPress/gutenberg/pull/76734))
* Site Editor > Quick Edit: Add form configuration to endpoint. ([76953](https://github.com/WordPress/gutenberg/pull/76953))
* Site Editor > Templates: Move configuration to the server. ([76622](https://github.com/WordPress/gutenberg/pull/76622))
##### Bug Fixes
###### Block Library
* Fix: Create custom template modal content width. ([76713](https://github.com/WordPress/gutenberg/pull/76713))
* Reduce the added halo for selected block. ([76619](https://github.com/WordPress/gutenberg/pull/76619))
* Revisions: Fix template revisions retrieval and sorting. ([76760](https://github.com/WordPress/gutenberg/pull/76760))
* Style Book: Fix missing styles for classic themes in stylebook route. ([76843](https://github.com/WordPress/gutenberg/pull/76843))
* Build: Remove unused JXL WASM module from vips worker. ([76639](https://github.com/WordPress/gutenberg/pull/76639))
* Gate client-side media processing as plugin-only. ([76700](https://github.com/WordPress/gutenberg/pull/76700))
* vips: Ensure single instance. ([76780](https://github.com/WordPress/gutenberg/pull/76780))
###### Data Layer
###### Site Editor
* Abilities: Improve JSDoc for public API. ([76824](https://github.com/WordPress/gutenberg/pull/76824))
* DOM: Document class wildcard matcher for ‘cleanNodeList’. ([76920](https://github.com/WordPress/gutenberg/pull/76920))
* Docs: Remove Puppeteer references and update to Playwright. ([76766](https://github.com/WordPress/gutenberg/pull/76766))
* Docs: Update PHP\_CodeSniffer repository link and schema URL. ([76816](https://github.com/WordPress/gutenberg/pull/76816))
* Storybook: Add redirect for moved introduction page. ([76701](https://github.com/WordPress/gutenberg/pull/76701))
* Storybook: Try changing to collapsed folders. ([76361](https://github.com/WordPress/gutenberg/pull/76361))
* UI Tooltip: Improve documentation to cover intended accessibility practices. ([76705](https://github.com/WordPress/gutenberg/pull/76705))
* Updating versions in WordPress ahead of 7.0. ([76723](https://github.com/WordPress/gutenberg/pull/76723))
* admin-ui: Update package README to clarify purpose and distinguish from ui package. ([76943](https://github.com/WordPress/gutenberg/pull/76943))
* docs(create-block-interactive-template): Document available variants in README. ([76831](https://github.com/WordPress/gutenberg/pull/76831))
* iAPI Docs: Add client-side navigation compatibility guide. ([76242](https://github.com/WordPress/gutenberg/pull/76242))
* Core Abilities: Fix sideEffects flag. ([76763](https://github.com/WordPress/gutenberg/pull/76763))
* Admin UI: Add CSS files to sideEffects array. ([76609](https://github.com/WordPress/gutenberg/pull/76609))
* admin-ui / Breadcrumbs: Stricter items[].to prop types. ([76493](https://github.com/WordPress/gutenberg/pull/76493))
* Refactor: Use null coalescing operator for improved readability. ([76777](https://github.com/WordPress/gutenberg/pull/76777))
* element: Make createInterpolateElement TS/type smart. ([71513](https://github.com/WordPress/gutenberg/pull/71513))
* Core Data: Optimize getRawEntityRecord selector. ([76632](https://github.com/WordPress/gutenberg/pull/76632))
* Core Data: Remove ‘isRawAttribute’ internal util. ([76806](https://github.com/WordPress/gutenberg/pull/76806))
* Navigation: Add a shared helper for font sizes in Navigation Link and Navigation Submenu blocks. ([74855](https://github.com/WordPress/gutenberg/pull/74855))
* Tab Block: Remove anchor from save function. ([76511](https://github.com/WordPress/gutenberg/pull/76511))
* Add TypeScript parser tests for shouldSkipReference. ([76611](https://github.com/WordPress/gutenberg/pull/76611))
* ESLint: Add no-unmerged-classname rule. ([76458](https://github.com/WordPress/gutenberg/pull/76458))
* create-block-interactive-template: Enhance block registration by using blocks-manifest for improved performance. ([76317](https://github.com/WordPress/gutenberg/pull/76317))
* Fix: Flaky RichText format end-to-end test. ([76958](https://github.com/WordPress/gutenberg/pull/76958))
* RTC: Add end-to-end block gauntlet. ([76849](https://github.com/WordPress/gutenberg/pull/76849))
* e2e: Add end-to-end tests for template and template part revisions. ([76923](https://github.com/WordPress/gutenberg/pull/76923))
* end-to-end Tests: Enable client-side media processing for site editor image test. ([76648](https://github.com/WordPress/gutenberg/pull/76648))
#### First-time contributors
The following PRs were merged by first-time contributors:
The following contributors merged PRs in this release:
[@aaronrobertshaw](https://github.com/aaronrobertshaw) [@adamsilverstein](https://github.com/adamsilverstein) [@aduth](https://github.com/aduth) [@alecgeatches](https://github.com/alecgeatches) [@andrewserong](https://github.com/andrewserong) [@annezazu](https://github.com/annezazu) [@aswasif007](https://github.com/aswasif007) [@carolinan](https://github.com/carolinan) [@CGastrell](https://github.com/CGastrell) [@chriszarate](https://github.com/chriszarate) [@ciampo](https://github.com/ciampo)[@DAreRodz](https://github.com/DAreRodz) [@dhasilva](https://github.com/dhasilva) [@dsas](https://github.com/dsas) [@ellatrix](https://github.com/ellatrix) [@epeicher](https://github.com/epeicher) [@gziolo](https://github.com/gziolo) [@im3dabasia](https://github.com/im3dabasia) [@ingeniumed](https://github.com/ingeniumed) [@jameskoster](https://github.com/jameskoster) [@jasmussen](https://github.com/jasmussen) [@jigangz](https://github.com/jigangz) [@jorgefilipecosta](https://github.com/jorgefilipecosta) [@jsnajdr](https://github.com/jsnajdr)[@juanmaguitar](https://github.com/juanmaguitar) [@Mamaduka](https://github.com/Mamaduka) [@manzoorwanijk](https://github.com/manzoorwanijk) [@maxschmeling](https://github.com/maxschmeling) [@meravi](https://github.com/meravi) [@mirka](https://github.com/mirka) [@ntsekouras](https://github.com/ntsekouras) [@oandregal](https://github.com/oandregal) [@pento](https://github.com/pento) [@ramonjd](https://github.com/ramonjd) [@retrofox](https://github.com/retrofox) [@rodrigoprimo](https://github.com/rodrigoprimo)[@sandipmaurya2611](https://github.com/sandipmaurya2611) [@scruffian](https://github.com/scruffian) [@senadir](https://github.com/senadir) [@sgomes](https://github.com/sgomes) [@Shekhar0109](https://github.com/Shekhar0109) [@shekharnwagh](https://github.com/shekharnwagh) [@shimotmk](https://github.com/shimotmk) [@SirLouen](https://github.com/SirLouen) [@Soean](https://github.com/Soean) [@t-hamano](https://github.com/t-hamano) [@talldan](https://github.com/talldan)[@tellthemachines](https://github.com/tellthemachines) [@Vedant-Gandhi](https://github.com/Vedant-Gandhi), What’s new in Gutenberg 22.9? (8 April), make.wordpress.org, 01kpggtbhqad5a93kc0twdjtq9.