François-Xavier de Guillebon

Interesting. I will be fine with adding a new file which contains only domains that are existing. But I will keep the `disposable_email_blacklist.conf` as it is currently and will not...

@ruudk @elchris @napestershine many PRs were merged on `master` to remove deprecations. Symfony 5 support is not yet ready there but it's a matter of time. @elchris could you rebase...

Symfony 5 is now supported on master.

@GKFX really nice, but could you split this PR in to smaller ones, please.

@BazyIPL @cpjolly A new `2.0` release is not planned for a near future (many things to adapt, opportunity to add BC breaks, ...). In the mean time, if you want...

@igorrebega before releasing a new major version (from master), CI should be fixed and probably migrated to Github Action (the phpunit part). If you have time to work on this,...

Let's tackle this, here's what I propose to do : - create 7.x branch - bump `elasticsearch/elasticsearch` to `^8.0` on master - bump minimum PHP version to `^8.0` on master...

Yes let's discuss this on a conversation ;) There was this one already: https://github.com/ruflin/Elastica/discussions/1961

This PR goal was to test the new `6.8.1` version of `elasticsearch/elasticsearch` published yesterday by @ezimuel . It seems it's still breaking on class `Elasticsearch\Endpoints\Indices\ForceMerge` which is not found anymore....

@ezimuel Don't know what to do on my side. This class renaming from `Elasticsearch\Endpoints\Indices\ForceMerge` to `Elasticsearch\Endpoints\Indices\Forcemerge` seems a bug on `6.8.1`. Recent version 7.12.0 has no issue as it uses...