Conversation
|
Flaky tests detected in 17ef976f7057b46b22efe80272ef7481f3054a77. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4368732969
|
|
@ockham @ockham seems like we could use a few canary tests in the compat layer to ensure basic operation (e.g. we don't introduce syntax errors on these backports) I think that with the work done lately to run PHP tests against a matrix of versions we might be able to do this once and have it check the 6.2 and 6.3 compat classe. I'll try to add them and explore |
fe3f85e to
15822ed
Compare
|
Updated from fe3f85e to 15822ed to also pull in the documentation changes. Followed the same method mentioned in the description. |
11c2dfc to
38f2d56
Compare
38f2d56 to
c6d69e1
Compare
What?
Blessed update pulling in updates to the HTML Tag Processor from Core into Gutenberg.
Related: WordPress/wordpress-develop@455b1e8
Why?
This process is being explored post 6.2 merge now that the HTML API development is occurring in Core.
Testing
Unit tests should pass, code should be audited. These changes should reflect the files in Core. They were generated by copying those files directly and then running
git a -pto include everything but the class rename.For the updates that landed here in Gutenberg head of Core (assuming those changes migrate into Core once the window for changes opens) I followed this procedure:
git add -pto include only the updatestrunkgit cherry-pickthe commit hash from the temporary branchThere were no merge conflicts this way, and I luckily didn't have to manually handle the addition of
has_bookmarkin Gutenberg.