Release 1.19.8

[twstokes]

The changes incorporated in the release 1.19.8 are:

• Retain Heading attribute when headings are autocorrected. #1334
• Fix Li tag when switching the list style (issue #1307) #1344

[twstokes]

My plan is to merge this once the following PRs are approved:

• Prevent bold headings after autocorrection gutenberg-mobile#4557
• [RNMobile] Prevent bold headings after autocorrection WordPress/gutenberg#38633

I did a smoke test with Mobile Gutenberg pointed to the changes for #1344 and it didn't appear affected. Running the Gutenberg Mobile demo and adding breakpoints here and here never paused execution when manipulating lists, telling me that Mobile Gutenberg doesn't use this path.

[twstokes]

@guarani would you mind taking a look at this release PR when convenient?

• The Gutenberg Mobile headings PRs are now approved [GB] [GB Mobile]
• I've done testing to determine that the changes from Fix Li tag when switching the list style (issue #1307) #1344 won't affect Mobile Gutenberg

Thanks! 🙇

[guarani]

The changes look good and match what I see in https://github.com/wordpress-mobile/AztecEditor-iOS/blob/develop/Documentation/ReleaseProcess.md.

I'm not familiar with the other change that's going into this release, but I presume it's also non-breaking, so can be shipped in a patch version.

I see you've checked the Gutenberg Mobile and Gutenberg demo apps with this change and there were no issues. Do we need to create a WPiOS PR, point it to this branch, and have its CI checks pass to know that WPiOS also works? I'm not sure this is needed though.
BTW even though WPiOS classic editor is powered by Aztec, classic editor tests are currently disabled , so I'm not sure CI would be able to catch any regressions anyway.

Should I do any manual testing of this release? Let me know how you want to proceed 🙇‍♂️

[twstokes]

I'm not familiar with the other change that's going into this release, but I presume it's also non-breaking, so can be shipped in a patch version.

Good thought: I think it qualifies for a patch in this case due to being a bugfix.

Do we need to create a WPiOS PR, point it to this branch, and have its CI checks pass to know that WPiOS also works? I'm not sure this is needed though.

Also a good thought. We'd tested the Headings bug independently, but I'll cut a branch to test this entire release just to be extra safe.

[twstokes]

I've created a PR in WPiOS to run CI for this release.

[guarani]

Approving since all looks good here from my perspective. I don't think manual testing is needed to review this and the WPiOS PR buildkite tests appear to be passing.