4.3.1 on Drupal 9.5.11 installs solarium 6.x-dev-b785b8b

Its worth noting that this also causes the module to report that its requirements aren't met in the Drupal Status Report as the module uses the Client::checkMinimal('6.2.3') check. which behind the scenes utilises version_compare(self::getVersion(), $version, '>=')

This fails as 6.x-dev is not seen as >= 6.2.3

The message presented is: Solarium @version is too old!

6.x-dev is actually a lot older than 6.2.3

Here's a patch for the github action.

@Greg Clout, the "issue" in #3 is not related to this one.

Will this still allow to install 4.3.1 on Drupal 9.5.11?

@hanoii I think theres a wider problem here. Drupal 9.5.11 requires symfony/event-dispatcher-contracts v1.1.13, but a dependency of this module is solarium/solarium which now requires symfony/event-dispatcher-contracts ^2.0 || ^3.0

Im not sure what the solution is here, as im currently trying to do a Drupal 10 upgrade from 9.5.11, but need to update the modules first

The "solution" is to upgrade to Drupal 10 first.
BTW Drupal 9 reached EOL.

Understood. Although I'd recommend if that's the case to maybe release a new version with only support for D10.

Because the fact that 4.3.1 installs but with a very old solarium library it's potentially dangerous, I actually found another project that I didn't upgrade under this same situation. Or maybe fix -dev on composer to match the actual latest so that dev is also not picked up by composer for 4.3.1?

D10 support was removed with 4.3.2.

To allow a dev version to fulfill requirements, there's a module or composer plugin.
But I didn't use that for a long time. To do such a transition you can use
composer require solarium/solarium:3.2.1 as 4.5.6 or composer require solarium/solarium:dev-master as 7.8.9

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

Hello @Greg Clout,

Do you know anything related the comment #3?

It seems I have the same issue.