Update constraint to allow or ECA 3

Wait a minute, I'll also update the deprecated namespace.

The remaining test failures are unrelated to this MR, so back to NR.

Facing the same issue.
Thanks for the MR

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/eca_vbo ^2.1 -> satisfiable by drupal/eca_vbo[2.1.0, 2.1.1, 2.1.x-dev].
    - drupal/eca_vbo[2.1.0, ..., 2.1.x-dev] require drupal/eca ^2.0 -> found drupal/eca[dev-2.0.x, dev-2.1.x, 2.0.0-alpha1, ..., 2.1.x-dev (alias of dev-2.1.x)] but the package is fixed to 3.0.0-rc1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Hoping for a commit and a tag release

The MR has a red cross sign, something is wrong there.

Those test failures are not related to the MR, they would be the same on the current dev branch.

The last commit in 2.1.x branch has green sign, this MR has a red sign. Maybe those checks don't even really make sense, but anyway, they were added once before by you: https://git.drupalcode.org/project/eca_vbo/-/blob/2.1.x/.gitlab-ci.yml?r...

An MR is ready for a review once it has a green sign.

Well, this module has last been tested 12 months ago. And it's tested against Drupal 11, which has changed quite a bit in that period.

The module doesn't successfully test against the current version of Drupal 11, and that should be fixes separately, not as part of this issue. The changes in this MR have NOT introduced those failures, they have just been unnoticed before.

Well, then we're blocked by those problems. So, we need a separate issue for fixing those problems first, flagging this issue to be blocked by that issue. Once that issue got fixed, then it unblocks this issue and we can continue to fix this issue.

Hoping for a soft 2.1.2-alpha1 release to speed up testing and using in Drupal 11.2

I don't know why I keep getting in the mess where I have to maintain modules that I haven't created. I've now also fixed the tests which only failed due to poor maintenance of the module that doesn't keep up with the changes upstream in the pipelines and with Drupal core.

Sorry if this sounds frustrated, that's because I am.