Problem/Motivation

Some of my projects need to test Drupal 11 as it is right now, since it contains features/changes that will not be merged to D10.

My projects also rely on Key as a dependency.

Key currently prevents Drupal 11.

Proposed resolution

Do you mind unlocking the constraint to allow D11, e.g with constraint like >=10.

Issue fork key-3395824

Command icon Show commands

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

dpi created an issue. See original summary.

dpi’s picture

my projects, being https://www.drupal.org/project/pusher_mini that relies on key.

https://www.drupal.org/project/sm tests d10 and d11.

https://www.drupal.org/project/toasty requries both of the above. Which I'd like to test w D10 + 11.

rlhawk’s picture

Version: 4.0.x-dev » 8.x-1.x-dev

rlhawk’s picture

I created a merge request, but I don't think we want to release a version of Key that claims to support Drupal 11. Can you use the Lenient Composer Endpoint (https://www.drupal.org/docs/develop/using-composer/using-drupals-lenient...) to add the module with Drupal 11?

ptmkenny’s picture

Now that Drupal 11 is in beta, is it possible to merge this to dev?

john franklin’s picture

Status: Active » Reviewed & tested by the community

This is functionally the same as the Project Bot patch in #3431507: Automated Drupal 11 compatibility fixes for key, and cleaner to boot. Tested against login_gov + oidc_connect + key_asymmetric.

Merging this will make it just a little bit easier for modules that depend on Key to test against D11.

rlhawk’s picture

Status: Reviewed & tested by the community » Fixed

Thanks. This has been merged.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.