- 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 the- info.ymlfile 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 infoBot run #11-120835- This patch was created using these packages: - drupal/upgrade_status: 4.1.0
- mglaman/phpstan-drupal: 1.2.7
- palantirnet/drupal-rector: 0.20.1
 
- Status changed to RTBCabout 1 year ago 3:50pm 13 September 2024
- 🇮🇳India abhi_khandelwal GandhinagarThe #MR3 works for both Drupal 10 and Drupal 11. Attaching the upgrade status screenshot for reference. 
- 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 the- info.ymlfile 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 informationBot run #11-392907- These packages were used to generate the fixes: - drupal/upgrade_status: 4.3.6
- mglaman/phpstan-drupal: 1.3.2
- palantirnet/drupal-rector: 0.20.3
 
- 🇺🇸United States joelsteidlThe MR is working well on a D 11.x site. - I created a new block
- I installed Condition Query module (from the MR)
- I limited the block to appear based on a condition query
- The block appeared when the condition query matched and didn't when it wasn't present.
 
- First commit to issue fork.
- 🇺🇸United States dwwNot sure why, and don't have time to further investigate, but the tests are still failing on D11, even with compatibility declared. 
- 🇺🇸United States dwwProbably https://www.drupal.org/node/3337193 → is the culprit 
- 🇺🇸United States dwwNope, still failing. I'm way out of time for this. If anyone wants to get the Kernel test passing on D11, knock yourself out. 😉 Thanks/sorry, 
 -Derek
- 🇺🇸United States dwwPushed some more commits. Test seems to be working now on all versions. 
- 🇺🇸United States dwwTagged https://www.drupal.org/project/condition_query/releases/8.x-1.5 → so I don't forget. 😂 
- 🇺🇸United States joelsteidlHuge shoutout to @dww for tagging a new release! Thank you. 
- Status changed to Fixed8 months ago 3:20pm 5 March 2025
- Automatically closed - issue fixed for 2 weeks with no activity.