[meta] Requirements for tagging 11.0.0-beta2

Filled in issues for jQuery 4 and jQuery UI.

Adding some known regressions to the issue summary.

Symfony 7.1 is done.

https://www.drupal.org/about/core/policies/core-release-cycles/schedule#... → lists RC1 for this week. Should this issue be retitled accordingly, or is a beta2 still on the table?

Yeah let's retitle it. The big one left here is 📌 Handling update path divergence between 11.x and 10.x Fixed

Opened 📌 Update Composer dependencies for 11.0.0-rc1 Needs review as there are a large number of patch level dependency updates that we should try to get into rc1.

Should we do something similar to 📌 Update Composer dependencies for 11.0.0-rc1 Needs review for JS-dependencies?

@Spokje: yes I think so. 📌 Upgrade JavaScript dependencies to latest minor/patch releases Fixed has standard steps.

Update subheaders to rc1 from beta1 in the issue summary.

Marking NR as I believe there are no issues outstanding that prevent us from releasing rc1.

only beta versions of jQuery and UI remains in beta, and there's no schedule for stable releases

Does this need to be merged first? 📌 Hardcode security coverage EOL dates for Drupal 10.last-1 and 10.last Needs review

@smustgrave no, that only matters for the 10.x branch really, as the warnings won't show in 11.x.

Moving some outstanding thingies to the 11.0.0 meta along with things we should check for again prior to release.

And yes the "hardcode dates" one is more of a should-have; it's only must-have for 10.4 (but the 10.4 meta isn't a thing on its own ATM due to it being a maintenance minor).

Automatically closed - issue fixed for 2 weeks with no activity.

Amending attribution.