Unfortunately it is not so easy. There were a number of changes in the API of aiida-core in v2.6 that we already adjusted to, amongst which the hashing. See bcc0129

The issue says

However, this dependency leads to conflicts with packages using aiida-pseudo that have yet to upgrade.

What are the specific problems? I think we should rather work to fix those than revert here.

The issue says

However, this dependency leads to conflicts with packages using aiida-pseudo that have yet to upgrade.

What are the specific problems? I think we should rather work to fix those than revert here.

I'll let @superstar54 explain. It was mostly a concern for those who use older versions of aiida-core AND aiida-pseudo.

As for the particular issue at hand, we're trying to release aiidalab-qe. All of our tests are running into an issue with aiida-pseudo w.r.t downloading the pseudos. This was "fixed" in #179, which already includes the ~=2.6 pin. This is now causing issues with the release due to aiidalab dependencies, but let me see if I can overcome those issues. I think it has already been tested with 2.6 and a new image is available. I'll check.

Hi @sphuber , thanks for the quick comment.

What are the specific problems? I think we should rather work to fix those than revert here.

We want to use aiida-pseudo inside the AiiDAlab docker image, which fixs aiida-core version==2.5.1.

We avoid the issue by using the latest AiiDAlab full-stack image with aiida-core 2.6.

As discussed with @edan-bainglass , we closed this PR.