Closed (works as designed)
Project:
Key
Version:
8.x-1.x-dev
Component:
Documentation
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2026 at 15:07 UTC
Updated:
21 Oct 2026 at 19:01 UTC
Jump to comment: Most recent
Comments
Comment #2
tbcs commentedOne data point for the 1.x question: the AI module requires
drupal/key ^1.18on every branch, including 1.5.1 and 2.0.x, so a site that uses an AI provider can't move to Key 2.x. On Drupal 12, Key 8.x-1.22 fails as soon asKeyPluginManageris constructed:So for those sites, Drupal 12 needs either attributes on 1.x (#3484086, !34) or an AI release that allows Key 2.x. !73 declares Drupal 12 for 8.x-1.x without the attributes, so on its own it would let Drupal 12 sites install a 1.x that can't load its plugins.
We ran into this in the Drupal 12 CI job of Site Agent.
Comment #3
joseph.olstadThere currently is no 2.0.x dev release. I wouldn't even worry about 2.0.x as they're not talking about it.
What the issue is here is that the rector picked up the 2.0.x branch and wrote the Drupal 12 rector fixes for it and skipped doing it for 8.x-1.x .
This is a rector issue, I will flag bbrala about this on drupal slack channels in the #d12readiness channel.
Comment #4
joseph.olstadComment #5
ptmkenny commentedHi as a co-maintainer of Encrypt, Field Encrypt, and other modules that are built on Key that needs to know to decide how we will be upgrading other Key ecosystem modules, please allow me to ask the maintainers for their decision.
Comment #6
joseph.olstadThis is more about a bug in the rector than anything. I reached out to @bbrala and he found the issue. A drupal 12 rector fix is coming soon which will make it easy to upgrade 8.x-1.x.
Comment #7
joseph.olstadhttps://drupal.slack.com/archives/C08QW79LJ94/p1792514567198949?thread_t...
Comment #9
joseph.olstadPublic knowledge, there's no such thing as can't. If a dependency is pinned to another major there are several ways to resolve.
composer require namespace/projectname:'2.0.0 as 1.22';and also something much more powerful: replaceThere's also several other possible solutions that I didn't mention.
Comment #10
ptmkenny commented@joseph.olstad Respectfully, do not close my issue that asks for maintainer comment unless you are a maintainer.
See, for example, #3483550: Add support for PHP attributes and require Drupal 10.2, where a maintainer suggests that attributes may not be added to 1.x. This was awhile ago so thinking may have changed, but I am seeking clarity on this specific point. If you found a bug in rector, great, report that in a different issue and don't close this one.
Comment #11
japerry1.x will support Drupal 12.