Issue #3594706: Add Drupal 12 support to core_version_requirement

Summary

Adds || ^12 to the module's .info.yml core_version_requirement, declaring Drupal 12 compatibility.

Verification

Re-ran Drupal Rector against the current 1.3.x HEAD (which includes all code the bot never saw — Phase 2 caching + PDF from MR !28 (merged), and the SDK 0.32 bump + regression test from MR !31 (merged)):

  • drupal-rector with drupal-10-all-deprecations config: 0 hits on the module.
  • phpcs (Drupal + DrupalPractice) on .info.yml: clean.
  • Full module unit suite: 84 tests, 153 assertions, green on SDK v0.32.0.

Deferred to drupalci pipeline: phpstan (workspace env has an unrelated contrib with a broken autoloader), cspell (not installed locally), PHPUnit concurrent variant, opt-in variants including OPT_IN_TEST_NEXT_MINOR which is what actually exercises the D12 target on CI.

Relation to prior work

Supersedes bot MR !29 which correctly diagnosed the same one-line change but scanned the module as of 2026-06-09 — pre Phase 2 (caching + PDF, merged 2026-06-26) and pre SDK 0.32 bump (merged 2026-07-01). This MR ports the same change onto current HEAD and confirms Rector remains clean over the new code.

AI-Generated: Yes

Used Claude Opus 4.8 to re-run Drupal Rector against current 1.3.x HEAD to verify the bot's diagnosis was still complete after Phase 2 and the SDK 0.32 bump landed, and to draft this MR description and coordinate closing the superseded bot MR. The one-line info.yml change itself is the same the Project-Update-Bot originally generated deterministically. Dependencies, logic, security, and GPL compatibility verified. Full contributor responsibility assumed.

Closes #3594706.

Merge request reports

Loading