- Issue created by @n4r3n
- 🇺🇸United States cmlara
Per #3324737: Do not support core versions newer than current published beta or higher → we will only push support AFTER Core releases a published beta.
We can however open an MR to start testing and ensure that there are no major issues already present.
- Status changed to Postponed
over 1 year ago 6:37am 18 November 2023 - 🇺🇸United States cmlara
On an initial test run this appears to be dependent upon 📌 Add Drush 12 support Active
- 🇧🇪Belgium aspilicious
Is there a reason we limit drupal 10 versions?
core_version_requirement: ^8.8 || ^9 || ~10.0.0 || ~10.1.0 || ~10.2.0
Why don't you add
core_version_requirement: ^8.8 || ^9 || ~10
- 🇺🇸United States cmlara
#3324737: Do not support core versions newer than current published beta or higher → covers the reasons why.
The goal is that we reduce the risk of taking down a site by more accurately reflecting the versions of core we work with. This policy is both for maintainer sanity (reduce the need for a critical hotfix) and for site owner sanity (they can expect that upgrading is generally safe).
It’s a policy I believe more modules on D.O. should consider adopting.
- Status changed to Active
over 1 year ago 4:00am 26 November 2023 - 🇺🇸United States cmlara
Drush 12 support in and core has released beta1, back to active.
Drush 12 support became more mandatory due to 🐛 Update drush conflict to "<12.4.3" RTBC
- Merge request !44Issue #3400038 by cmlara, n4r3n: Add support for Drupal 10.2 → (Merged) created by cmlara
- Status changed to Fixed
over 1 year ago 7:36am 4 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.