Gutenberg: v10.3.x plugin upgrade

[fullofcaffeine]

Previous upgrade: #50775
Release notes: v10.3.0, v10.3.1, v10.3.2

Process

• Install and activate
  • Copy & install v10.3.0-rc.1
  • Activate v10.3.0-rc.1 on edge
  • Copy & install v10.3.0 (D59599-code, D59601-code)
  • Activate v10.3.0 on edge (D59602-code)
  • Activate v10.3.0 on production (D59463-code)
  • Request update for Atomic sites (p9o2xV-1kL-p2)
  • Revert to v10.2.0 (D59623-code)
  • Re-activate v10.3.x on production once Hever: Extra white space / margin in the Block editor  themes#3599 is fixed
  • Unblock the Atomic request (p9o2xV-1kZ-p2)
  • Copy & install v10.3.2 (D59858-code, D59860-code)
  • Activate v10.3.2 on edge (D59861-code)
  • Activate v10.3.2 on production (D59862-code)
  • Request Atomic upgrade for v10.3.2 (p9o2xV-1lk-p2)
• Testing
  • Calypso E2E (Gutenberg: Fix E2E suite against v10.3.0 #51525, Gutenberg: Run E2E upgrade suite against v10.3.2 #51752)
  • Team City (D59463-code)
  • Revert Calendar bug hotfix (Gutenberg: Revert E2E hotfix after production rollback #51625)
• Publish internal announcements (p7DVsv-b3y-p2, p1617259479193200-slack-CB0B2G43X)
• 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 🙅‍♀️

• Broken themes' properties that use experimental features
  • Reported in: Hever: Extra white space / margin in the Block editor  themes#3599
  • Slack context: p1617267873288500-slack-C7YPUHBB2
  • Caused a revert to v10.2 (D59623-code)
  • Fixed in v10.3.1

Other issues 🐛

• Default font for non-FSE themes missing
  • Reported in Multiple Themes: Editor font styles not loading in Gutenberg v9.9.3 themes#3280
  • Upstream fix: Restore the default editor font for the non FSE themes WordPress/gutenberg#30080 (will be included with v10.3.0)
  • Hotfixed on Simple sites via D59109-code
  • Slack context: p1616412181032500-slack-C7YPUHBB2
• Opting out of the widgets-block-editor theme support crashes the editor serverside (blocker, it crashes the editor and frontend on WPCOM)
  • Originally reported on Slack in: p1616697969125400-slack-C7YPUHBB2
  • Issue: Opting out of the widgets-block-editor theme support crashes the editor serverside WordPress/gutenberg#30305 (thanks @draganescu!)
  • Fix: Widgets: Fix warning when widgets block editor is disabled WordPress/gutenberg#30318 (thanks @noisysocks!)
  • Hotfixed in 10.3.0-rc.1 in the activation diff, will be included in the 10.3.0 stable release.
• @-mentions broken when more than one used inline
  • Reported in p1617641512194600-slack-C010KDAPG49
  • Fixed in Components: Query autocomplete by the term from last trigger prefix character WordPress/gutenberg#30540
  • Fix will be included in v10.3.2

---

FYI: @Automattic/team-calypso

[WunderBart]

Before the next (v10.4) upgrade: Make sure to test WordPress/gutenberg#30231. Context: p1616675249116100-slack-C7YPUHBB2. cc @simison

[WunderBart]

Due to a regression in v10.3 that affected 9 themes, we've decided to revert production to v10.2. See p1617267873288500-slack-C7YPUHBB2 for more info.

[WunderBart]

Another issue with v10.3.2 that causes OOM errors on P2 posts where the Latest Posts block was used (FYI that block has been permanently disabled some time ago, so that might be the cause of this issue). We were able to determine that this is a P2-only issue and happens only for the v10.3.2 release. Both previous v10.3.1, and next v10.4.0-rc.1 does not seem to cause this issue. Context:

• p9oQ9f-th-p2
• p1617880554267800-slack-C010KDAPG49

[WunderBart]

Next one: #51767