- last update
over 1 year ago 1 pass - last update
over 1 year ago 1 pass - Issue was unassigned.
- Status changed to Needs review
about 1 year ago 11:31am 2 December 2023 - Status changed to Needs work
9 months ago 7:42am 23 March 2024 - 🇮🇹Italy apaderno Brescia, 🇮🇹
The issue summary should always explain why the change is necessary.
Why does this module need to be marked deprecated for Drupal 9.4.5? The module is already marked deprecated with
lifecycle: deprecated. Is there any reason to mark it deprecated specifically for Drupal 9.4.5? - 🇮🇹Italy apaderno Brescia, 🇮🇹
-core_version_requirement: ^9 +core_version_requirement: ^9 || ^10If it is deprecated, it does not need to declare its compatibility with Drupal 10.