Fixed
Project:
Accessible External Link
Version:
1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Jul 2026 at 15:31 UTC
Updated:
6 Jul 2026 at 15:46 UTC
Jump to comment: Most recent
Follow-up to the Project Update Bot issue #3598063, done with test coverage and CI verification rather than only declaring compatibility.
Problem
The module declares core_version_requirement "^10.3 || ^11" and does not test against the next major version in CI (OPT_IN_TEST_NEXT_MAJOR is commented out in .gitlab-ci.yml), so Drupal 12 compatibility is unverified. The field formatter also has no automated test coverage.
Proposed resolution
Remaining tasks
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
mably commentedMR !11 is green, including the next-major (Drupal 12) jobs: after enabling OPT_IN_TEST_NEXT_MAJOR, composer, phpstan and phpunit all pass against Drupal 12. So the "^12" core_version_requirement is now backed by a real Drupal 12 test run, not only a Rector scan. The MR also adds kernel test coverage for the field formatter, which previously had none. Supersedes the Project Update Bot issue #3598063.
Comment #5
mably commented