- Issue created by @Project Update Bot
- last update
8 months ago 1 pass 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 โ , 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.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-120024This patch was created using these packages:
- drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
- last update
8 months ago 1 pass - last update
8 months ago 1 pass 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
- last update
8 months ago 1 pass - ๐ญ๐บHungary Balu Ertl Budapest ๐ช๐บ
Balu Ertl โ made their first commit to this issueโs fork.
- last update
6 months ago 1 pass - ๐ญ๐บHungary Balu Ertl Budapest ๐ช๐บ
Blocked by ๐ PHP 8.2 deprecation issue with AutosaveFormBuilder Needs work .
- ๐ญ๐บHungary Balu Ertl Budapest ๐ช๐บ
Not parent but related issue, sorry.
- Status changed to RTBC
6 months ago 3:24pm 27 May 2024 - ๐ญ๐บHungary Balu Ertl Budapest ๐ช๐บ
Tested on a D11-beta1 website (patched with the aforementioned deprecation fix). Installing, then configuring the module, testing with a node add, then edit form, finally uninstalling all found working as expected, therefore I think it's ready to merge.
- Status changed to Needs review
6 months ago 6:33am 2 June 2024 - last update
6 months ago 1 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 โ 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-188138These packages were used to generate the fixes:
- drupal/upgrade_status: 4.3.2
- mglaman/phpstan-drupal: 1.2.11
- palantirnet/drupal-rector: 0.20.2
- last update
6 months ago 1 pass - ๐ฎ๐ณIndia chandu7929 Pune
chandu7929 โ changed the visibility of the branch project-update-bot-only to hidden.
- First commit to issue fork.
- ๐ฎ๐ณIndia ankitv18
Pushed minor change ~~ MR changes are quite straightforward. Marking this one RTBC
- ๐ฎ๐ณIndia vipin.mittal18 Greater Noida
Hello @hchonov,
I hope youโre doing well! Iโm reaching out to ask about the release plans for this module with Drupal 11 compatibility. Any updates on the timeline would be greatly appreciated. Thanks!
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
hchonov โ changed the visibility of the branch project-update-bot-only to active.
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
hchonov โ changed the visibility of the branch project-update-bot-only to active.
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
hchonov โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
hchonov โ changed the visibility of the branch project-update-bot-only to hidden.
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
hchonov โ changed the visibility of the branch project-update-bot-only to active.
- ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
I've merged only what the Automated Project Update Bot did, not sure why the other commits were done. I will test this with Drupal 11 and if all works fine I will tag a new release.
- ๐ฎ๐ณIndia ankitv18
The difference between the project bot MR and other MR is project consists of core_version_requirement constraints in autosave_form_test.info.yml instead of testing package
Also non-project bot MR consists of gitlab CI file to execute the pipelines. - ๐ฉ๐ชGermany hchonov ๐ช๐บ๐ฉ๐ช๐ง๐ฌ
Feel free to create a new issue for this please. A new version supporting D11 was just released.