Incompatibility with the external_entities module

Is it possible to just widen the requirements to ^1 || ^2 instead of dropping support for ^1?

Per https://github.com/Galbar/JsonPath-PHP/blob/master/CHANGELOG.md I don't see any breaking changes but it does modify some behavior. Honestly it could probably be updated to: ^1 || ^2 || ^3.

I am having trouble with updating my composer lockfile - I keep getting the error about galbar/jsonpath version. The setup has both drupal/next (requires subrequests) and drupal/external_entities modules that require galbar/jsonpath:

  Problem 1
    - Root composer.json requires drupal/external_entities ^2.0@beta -> satisfiable by drupal/external_entities[2.0.0-beta1].
    - drupal/external_entities 2.0.0-beta1 requires galbar/jsonpath ^2.0 -> found galbar/jsonpath[2.0, 2.1] but the package is fixed to 1.3.1 (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.

I do have the patch from this issue, also tried patching locally. I am now suspecting composer somehow check the dependencies before patch is applied and stops me from updating lockfile.

Would it be possible to have patched version released that allow "galbar/jsonpath": "^2.0", requirement? Thanks!

This is a big blocker for normal composer workflow. We're using this for a month now and looks like its working as expected and does not create any issues.

Any update on this to get this merged at least?

"galbar/jsonpath": "^1.0 || ^2.0 || ^3.0"

Why changing status to needs work? Can you explain what the next steps would be, if any?

To me, this is still RTBC

Yes, more like "Need attention".