Latest 6.1 RC1 requires Drupal 10.1 and forces upgrade

Thanks for asking about this.

The backstory of why there is a Drupal 10.1-compatible release is in 📌 LinkIt requires new minor version for Drupal 10.1.x, since CKEditor 5 got a major version update (v35 → v36) Fixed .

We wanted to tag a D 10.1-compatible release of Linkit *prior* to the release of Drupal 10.1 so that it would not prevent people from updating when Drupal 10.1 is released.

Fear not: with the right directives in Composer, you can get the version of Drupal and the version of Linkit that you want. The 6.0.0-rc1 release of Linkit is designed to work with Drupal: ^9.4 || <10.1.

I would guess that you are getting the pre-release version of Drupal 10.1 because of your minimum-stability configuration in composer.json

If you specify drupal/core: "^10@stable", your update will not go to Drupal 10.1 yet (and it will retrieve the 6.0.0-rc1 release of Linkit rather than 6.1.0-rc1

See https://getcomposer.org/doc/04-schema.md#package-links

Ah yes thank you! This is very helpful and hopefully helpful to others as well.

Yes I have the global minimum stability set to "dev" because I sometimes have to use dev versions of modules for one reason or another. I didn't know you could still specify the desired stability for individual packages. So now I've done that and it's solved the problem.

GaëlG → made their first commit to this issue’s fork.

I'm going to close this issue, since based on the response above, and a similar report at 🐛 composer update installs Linkit 6.1 even if I use Drupal core 10.0 Closed: works as designed , the releases and constraints for LinkIt, itself, are not the root cause, but rather other Composer configuration directives.