Over at the Drupal integration, we've received an issue, that IPv6 is not supported by this package. You can find all the details at https://www.drupal.org/project/crowdsec/issues/3333436

Is there anything we can do on the Drupal integration to make this work, or is IPv6 indeed not supported? If so, are you planning to add IPv6 support in the future?

Sorry, to mis-use this channel for this approach, but I'm trying to get hold of Julien Devouassoud and all channels I have seem to be failing. He wrote to me and I responded and also send emails some time ago. No response at all and I'm worries that my email isn't getting through to him.

Also tried to reach him on Slack, no response either.

Could someone here in this issue queue who has a chance trying to ping him and letting him and me know, how we could communicate efficiently? Thanks in advance.

Currently, the dependency to the other packages are very strict and difficult to upgrade. As the constraints don't allow for higher version numbers but require a very specific version, a composer update can easily fail, because the composer.lock file contains that earlier fixed version and doesn't allow to update to the new one, unless the lock file gets deleted first.

But that's not an ideal workflow for composer based applications.

Instead of declaring

    "require": {
        "crowdsec/capi-client": "0.11.0",
        "crowdsec/lapi-client": "0.4.0",
    },

it would be better to something like this:

    "require": {
        "crowdsec/capi-client": "^0.11",
        "crowdsec/lapi-client": "^0.4",
    },

However, we've also seen issues with 0-based version numbers in the past. So the extended version of the question would be, when you're planning to go for something like 1.0.0-alpha at least?