Gutenberg: v10.6.x plugin upgrade

[fullofcaffeine]

Previous upgrade: #51997
Release notes: v10.6.0-rc.1, v10.6.0, v10.6.1, v10.6.2.

• Install and activate
  • Copy & install v10.6.0-rc.1 (D61047-code, D61048-code)
  • Activate v10.6.0-rc.1 on edge (D61049-code)
  • Hotfix v10.6.0-rc.1 on edge to fix the WSOD issue (more details below) (D61090-code, D61091-code)
  • Copy & install v10.6.0 (D61298-code, D61302-code)
  • Activate v10.6.0 on edge (D61304-code)
  • Hotfix v10.6.0 on edge to fix the WSOD issue (more details below) (D61305-code, D61307-code)
  • Copy & install v10.6.1 (D61541-code, D61543-code)
  • Activate v10.6.1 on edge (D61546-code)
  • Hotfix v10.6.1 on edge to fix the WSOD issue (more details below) (D61544-code, D61545-code)
  • Copy & install v10.6.2 (D61671-code, D61674-code)
  • Activate v10.6.2 on edge (D61675-code)
  • Hotfix v10.6.2 on edge to fix the WSOD issue (more details below) (D61677-code, D61679-code)
  • Make sure there are no active blockers
  • Activate v10.6.2 on production (D61050-code)
  • Request AT upgrade
• Testing
  • Desktop viewport E2E
  • Mobile viewport E2E
  • WPCOM Backend (D61050-code)
• Publish internal announcements
• Clean up unused releases
• Add log entry to the Gutenberg Upgrade Log [pcoGjb-g-p2]
• Open a new issue for the next upgrade, transfer remaining tasks, close this issue.

Blockers 🙅‍♀️

• Premium Content block is breaking. Fix: Premium Content Block: Update to useBlockProps jetpack#19844.

This has been fixed in the PR and merged, but is yet to be deployed to WPCOA/WoA. Even though we could get it on simple sites now, it's best to wait until the next Jetpack release on June 1st for the new JP release or people that upgrade to WoA will get invalidation errors with the Premium Content block. More details in this thread: p1621442044054200-slack-CBG1CP4EN.

• Disable features and add sticker toggles (p9oQ9f-vj-p2#comment-920, p1620735562081300-slack-C7YPUHBB2):

  • Block Widgets (D50432-code)
  • Navigation Block (p9oQ9f-vj-p2#comment-928)
  • Template Editing (D61453-code, D61455-code)

• Necessary JP blocks updates (p1620817101206900-slack-CBTN58FTJ)

  • Blocks: switch away from __experimentalBlock to useBlockProps jetpack#18864
  • Remove the block wrapper component WordPress/gutenberg#31419

Other issues 🐛

From the new release

• wp-components's index.js is broken by the WPCOM minifier. There's a hotfix (D61090-code, D61091-code) applied in the RC1 that allowed us to ship it to simple sites for now. We still don't know what exactly in v10.6.0 RC1 caused this. We might need to be hotfixing on simple sites while we don't have a perm. solution. See: p1620321684463200-slack-C02A41GCS and p1620319065221200-slack-C4GAP2RHD.
  • Generate minified .min.js and unminified .js files for GB js entry points when building WordPress/gutenberg#31732
• P2 inline comments broken (and potentially other P2-related issues). Reported here: p1620327615008700-slack-C025Q5RK2 cc @johngodley (P2s have been pinned to 10.5.4 for now, see: p1621258202222400/1620838719.129600-slack-C7YPUHBB2, which makes this issue not a blocker for now).

Transfered from previous release(s)

• Classic: Infinite content duplication loop when wrapping with anchor tag #29338
  • Reported in: p1613735197155300/1613458151.107400-slack-CBTN58FTJ
• Search block's button padding is broken
  • Reported here: Broken padding in Search block's button WordPress/gutenberg#29952

---

cc @inaikem

[WunderBart]

@jeherve mentioned that we'd need to update 2 JP blocks before releasing this version. See p1620817101206900-slack-CBTN58FTJ for more info. I've added this as a blocker (see issue description).

[simison]

BTW IE11 support is out with this one. :-)

This release marks a milestone in modern web development. As of Gutenberg 10.6, we have officially dropped support for Internet Explorer 11, in accordance with the IE 11 Support Phase-Out Plan. This change effectively reduces the total build size by a whopping 6%.

https://make.wordpress.org/core/2021/05/14/whats-new-in-gutenberg-10-6-12-may/

[simison]

I see two more instances of __experimentalBlock, assuming those are still blocking the upgrade? (issue Automattic/jetpack#18864)

https://github.com/Automattic/jetpack/search?q=__experimentalBlock

[fullofcaffeine]

We won't be able to upgrade WPCOM (simple sites and WoA) to Gutenberg 10.6.x / 10.7.x until after the next Jetpack version is released, scheduled to happen on June 1st. This is due to JP including fixes to issues in the Premium Content block caused by changes in 10.6.x. More details here: p1621442044054200-slack-CBG1CP4EN.

[WunderBart]

Dropping this one here for awareness: #53008

[fullofcaffeine]

I've created the tracking issue for v10.7.x, here. I'll keep this open until we update edge to v10.7.x, which is blocked until we ship #53131. v10.6.x never got beyond edge due to blockers listed above (also see: p1621444728022400/1621357342.009900-slack-C7YPUHBB2).