- Issue created by @project update bot
- last update
10 months ago 8 pass 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 → , even with these changes, this module is not yet compatible with Drupal 11.
Currently Drupal Rector, version 0.20.1, cannot fix all Drupal 11 compatibility problems.
Therefore these changes did not update the
info.yml
file for Drupal 11 compatibility.The compatibility issues that Upgrade Status found after the Drupal Rector fixes were applied are attached to help you resolve them manually.
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-127659These packages were used to generate the fixes:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.9
- palantirnet/drupal-rector: 0.20.1
- last update
10 months ago 8 pass - Status changed to RTBC
6 months ago 4:24am 3 August 2024 - Assigned to Grevil
- Status changed to Needs work
5 months ago 9:41am 27 August 2024 - 🇩🇪Germany Grevil
There are still loads of D11 compatibility issues (e.g. core_version_requirement).
- Issue was unassigned.
- Status changed to Needs review
5 months ago 9:55am 27 August 2024 - Status changed to RTBC
5 months ago 6:17pm 27 August 2024 - First commit to issue fork.
-
graber →
committed ad9d0c75 on 8.x-2.x authored by
Project Update Bot →
Issue #3435419: Automated Drupal 11 compatibility fixes for...
-
graber →
committed ad9d0c75 on 8.x-2.x authored by
Project Update Bot →
- 🇵🇱Poland Graber
Merged. I'm totally busy recently and not even using this module on any of my current projects so it'd be nice if someone could help at least releasing new changes.
- Status changed to Fixed
5 months ago 9:48am 28 August 2024 - 🇩🇪Germany Grevil
@graber feel free to add @Anybody and me as maintainers!
You can check our profile for references. Cheers!
- 🇨🇦Canada joseph.olstad
Hello, I was pinged about this outstanding issue and noticed that the most recent release was tagged and released by myself. However I just checked and noticed that I'm no longer listed as a maintainer on this project. So it looks like someone removed me as a maintainer without telling me. Anyhow, good luck!
- 🇩🇪Germany Anybody Porta Westfalica
@joseph.olstad I have no idea who did that and why, but I just re-added you as co-maintainer!
- 🇮🇳India ankitv18
Hi,
This change https://git.drupalcode.org/project/views_bulk_edit/-/commit/ad9d0c75555e... needs to be handle for backward compatibility.
Should be open a new issue or should be fix here only?
cc: @anybody @joseph.olstad @grevil - 🇩🇪Germany Anybody Porta Westfalica
@ankitv18 please open a new issue for that, thanks!
- 🇩🇪Germany Grevil
I don't think it needs backwards compatibility. We do not opt into previous major tests (D9), meaning that the tests will never automatically run in a D9 environment, hence we do not need any backwards compatibility for "EntityReferenceFieldCreationTrait".
- 🇩🇪Germany Grevil
I think we should even drop the D9 compat and create a new 3.x branch (after we fixed the pipeline). What do you think @Anybody?
Automatically closed - issue fixed for 2 weeks with no activity.