Update dependency @lezer/lr to v1.4.3

[matticbot]

This PR contains the following updates:

Package	Change	Age	Confidence
@lezer/lr	1.4.2 -> 1.4.3

---

Release Notes

lezer-parser/lr (@​lezer/lr)

v1.4.3

Compare Source

Bug fixes

Fix an issue that caused some skipped nodes to incorrectly become children of the node before them.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 02:59 AM, on day 1 of the month ( * 0-2 1 * * ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the renovate/lezer-lr-1.x branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack renovate/lezer-lr-1.x

bin/jetpack-downloader test jetpack-mu-wpcom-plugin renovate/lezer-lr-1.x

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[tbradsha]

Seems safe.