- Issue created by @BramDriesen
- πΊπΈUnited States damienmckenna NH, USA
Have seen this on Block Visibility Groups:
https://www.drupal.org/project/block_visibility_groups/issues/3428250 π Automated Drupal 11 compatibility fixes for block_visibility_groups Closed: duplicate
https://www.drupal.org/project/block_visibility_groups/issues/3428279 π Automated Drupal 11 compatibility fixes for block_visibility_groups Needs reviewBoth issues were against the 2.0.x branch, both have a patch added and an issue fork named "ISSUENUMBER-automated-drupal-11", but the newer one also has a merge request named "project-update-bot-only".
Darn, see another:
https://www.drupal.org/project/issues/ala?categories=All β
Canceled current run to try and investigate how this happens.
- π§πͺBelgium BramDriesen Belgium π§πͺ
Oh wow, that's a bad case indeed
-
bbrala β
committed 8aa6bdbf on master-d11
feat: for projects with real version numbers also do the prefix check so...
-
bbrala β
committed 8aa6bdbf on master-d11
- Status changed to Fixed
over 1 year ago 9:50am 22 April 2024 - π³π±Netherlands bbrala Netherlands
Found a fix fore the issue. After refactoring it assumed no more old school version's therefor it did not check against version with a prefix. This unfortunately is still needed.
Validated in local test run, it now finds the issues.
Automatically closed - issue fixed for 2 weeks with no activity.