- 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 (MR) 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 or merging the MR, will allow the Project Update Bot → to post additional Drupal 11 compatibility fixes as they become available in Drupal Rector.
Debug information
Bot run #11-217342These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.4
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.3
- Status changed to Needs review
5 months ago 7:52pm 6 July 2024 - Status changed to RTBC
3 months ago 6:15am 2 September 2024 -
heikkiy →
committed 7b6e5222 on 1.0.x authored by
Project Update Bot →
Issue #3459661 by kekkis, heikkiy: Automated Drupal 11 compatibility...
-
heikkiy →
committed 7b6e5222 on 1.0.x authored by
Project Update Bot →
- Status changed to Fixed
3 months ago 12:57pm 6 September 2024 - 🇳🇱Netherlands joshahubbers
Hi Heikkiy,
When I look at the table here https://www.drupal.org/docs/distributions/degov/semantic-versioning-model → it suggests:
0.0.x = patch version for bugfix
0.x.0 = minor version update with new features that do not break functionality
x.0.0 = major, new features, breaking backwards compatability.Well, this upgrade doesn't really add new functionality, so I think your decision to go to 1.0.4 is totally fine ;-).
Thanks for your collaboration!
Automatically closed - issue fixed for 2 weeks with no activity.