Hello @ebolyen
thank you for offering further support with these plugins. This issue has been already discussed earlier Qiime2 Library Compatibility
Taken together, I applied these ‘workarounds’ to get gemelli and qurro running in q2-2025.4 and q2-2025.10 (I just tried it 
).
pip install Cython==0.29.37
pip install iow==1.0.7
pip install empress
pip install gemelli
conda install -c conda-forge qurro
In particular, qurro installation displays this info:
added / updated specs:
- qurro
The following packages will be downloaded:
package | build
---------------------------|-----------------
certifi-2026.1.4 | pyhd8ed1ab_0 147 KB conda-forge
qurro-0.9.0 | pyhd8ed1ab_2 440 KB conda-forge
------------------------------------------------------------
Total: 588 KB
The following NEW packages will be INSTALLED:
qurro conda-forge/noarch::qurro-0.9.0-pyhd8ed1ab_2
The following packages will be UPDATED:
ca-certificates 2025.10.5-hbd8a1cb_0 --> 2026.1.4-hbd8a1cb_0
certifi 2025.10.5-pyhd8ed1ab_0 --> 2026.1.4-pyhd8ed1ab_0
openssl 3.5.4-h26f9b46_0 --> 3.6.1-h35e630c_1
The following packages will be SUPERSEDED by a higher-priority channel:
iow pypi/pypi::iow-1.0.7-pypi_0 --> bioconda/linux-64::iow-1.0.5-py310hc31ed2c_5
Here, iow is downgraded again to 1.0.5, but I do a second pip install iow==1.0.7 and it seems to work.
I did not export and re-import some data as suggested, since I do use provenance intensively when writing manuscripts (replay-provenance) and I would like to keep my own workflow simple, e.g. without ex-/importing steps.
I can well imagine how complex qiime2 has become, and versioning is certainly a huge challenge. However, if I could use external plugins without workarounds, it would give me more confidence that incompatible dependencies would not be introduced.
A big thank you to everyone in the qiime2 team, both immediate and extended, for this great tool.
Best,