Gutenberg: v10.1.x plugin upgrade

[WunderBart]

Previous upgrade: #50060
Release notes: v10.1.0, 10.1.1

Process

• Install and activate
  • Copy & install v10.1.0-rc.1 (D57602-code, D57605-code)
  • Activate v10.1.0-rc.1 on edge (D57608-code)
  • Copy & install v10.1.0 (D58006-code, D58008-code)
  • Activate v10.1.0 on edge (D58009-code)
  • Activate v10.1.0 on production (D57609-code)
  • Request update for Atomic sites (p9o2xV-1hM-p2)
  • Copy & install v10.1.1 (D58202-code, D58203-code)
  • Activate v10.1.1 on edge (D58205-code)
  • Activate v10.1.1 on production (D58206-code)
  • Request update for Atomic sites (p9o2xV-1id-p2)
• Testing
  • Calypso E2E (Gutenberg: Trigger E2E edge suite against v10.1.1 #50447)
  • Team City (D57609-code)
• Publish internal announcements
• Clean up unused releases
  • v9.9.3 (D58139-code)
  • v10.1.0-rc.1 (D58141-code)
• Update the Gutenberg Upgrade Log [pcoGjb-g-p2] and list patches applied
• Open a new issue for the next upgrade, transfer remaining tasks, close this issue.

Issues / Blockers 🐛

• Block's focus stealing regression

  • Discovered via E2E: Gutenberg: Trigger E2E edge suite against v10.1.1 #50447 (comment)
  • Reported in: Previously-focused block steals focus from blocks added by the main inserter  WordPress/gutenberg#28932 (comment)
  • Upstream fix: Fix mobile inserter focus behavior WordPress/gutenberg#29342 (will be included in v10.1.0)
  • Slack context: p1614255122109100-slack-C02A41GCS

• Classic: Infinite content duplication loop when wrapping with anchor tag #29338 (not a blocker)

  • Reported in: p1613735197155300/1613458151.107400-slack-CBTN58FTJ

• Reusable block can't be broken down into individual blocks, no specific root cause identified yet. Seems specific to using some blocks inside the reusable block, though it's not known yet at this time. (edge case / not a blocker)

  • Reported in: p1614866772382300-slack-C7YPUHBB2

• Crashing editor/browser when latest Instagram posts block is added (this would probably be considered a blocker for the release, but unfortunately we only found it after releasing. A talk about regression test starts here: p1614903492124800/1614895798.108900-slack-CBTN58FTJ).

  • Reported in: Gutenberg v10.1.0 - Crashing editor/browser when latest Instagram posts block is added #50778
  • Slack context: p1614895798108900-slack-CBTN58FTJ
  • JP fix: Fix instagram infinite loop bug jetpack#19034;
  • Gutenberg fixes:
    • withNotices: Ensure that the callback props are stable. WordPress/gutenberg#29491;
    • withNotices: Memoize the noticeOperations object WordPress/gutenberg#29582.

---

FYI: @Automattic/team-calypso

[fullofcaffeine]

This is done 🎉! Next one: #50775.

[fullofcaffeine]

Re-opening due to #50778 (slack context: p1614895798108900-slack-CBTN58FTJ). A patch-release including the fix has been released already. I'll close once the update is done.