Update Klaro! libraries

I have updated the 3.0.x branch of the klaro_js library → which made the latest version available at https://packagist.org/packages/drupal/klaro_js#3.0.x-dev

What would be great, if the composer.json of the Klaro module could declare the constraint like this:

        "drupal/klaro_js": "^3.0 || ^3.0.x-dev"

That way, Drupal projects would load the latest 3.0 stable release, but if we add the dev requirement in a Drupal project for development, we could force the usage of the dev version without having to make any changes to the module ever.

I changed the composer.json. Now we can install the dev version for testing.

But I expect the versions to be dependent on each other in the future, so I would prefer to have some control of the requirement and use ~3.0.0.

Then we could publish the new klaro_js with breaking changes independent from klaro module and use it for testing the dev-version of klaro.

And in case of security updates we have to update klaro module every time, because an update of klaro_js ist not visible in the Drupal update report.
And we have to guarantee backwards compatibility, which doesn't work if the systems automatically update the library but not the module.

So I would prefer ~ requirement

        "drupal/klaro_js": "~3.0.0 || ^3.0.x-dev"

We probably don't even need the || ^3.0.x-dev part. I've tried in a project with the Klaro module dev release and required the dev release of the library in the project, which still works, even though the module requires ^3.0.

So, it would be sufficient to require ~3.0.0 as you described.

I changed to ~3.0.0 in Dev.

New version is tagged. Thanks to @jurgenhaas!