- Issue created by @project update bot
This is an automated patch generated using Upgrade Status and Drupal Rector. Please see the issue summary for more details. A merge request is also openend and updated.
It is important that any automated tests available are run and that you manually test the changes.
Drupal 11 Compatibility
According to the Upgrade Status module β these changes make this module compatible with Drupal 11! π
Therefore these changes update theinfo.yml
file for Drupal 11 compatibility.Leaving this issue open, even after committing the current patch, will allow the Project Update Bot β to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug info
Bot run #11-120835This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- π¦πͺUnited Arab Emirates beautifulmind Dubai
Hi,
Do you have any plans to merge these enhancements and create a new release for Drupal 11?
Kind regards.
-
nevergone β
committed 74cfa3cc on 3.x
Issue #3429028: Automated Drupal 11 compatibility fixes for blog
-
nevergone β
committed 74cfa3cc on 3.x
- π¨π¦Canada smulvih2 Canada π
@nevergone, you committed the change to the *.info file, but not to composer - https://git.drupalcode.org/project/blog/-/commit/74cfa3ccc8a8a14d51ad1b1596eea1527ec76fe9
Still need change in this patch.
- π¨π¦Canada smulvih2 Canada π
Need the above fixed before I can get
drupal/blog
pulled into my project with composer. -
nevergone β
committed 2e0ba0f8 on 3.x
Issue #3429028: Automated Drupal 11 compatibility fixes for blog
-
nevergone β
committed 2e0ba0f8 on 3.x
- ππΊHungary nevergone NyΓregyhΓ‘za, Hungary, Europe
Thanks, I created a new release.
^10.4 || ^11.1
Automatically closed - issue fixed for 2 weeks with no activity.