We have a case where we needed a wave container for the newer conda build of multiqc-1.35 (multiqc=1.35=pyhdfd78af_1).
We already have a container for the previous build https://wave.seqera.io/view/builds/bd-cb7458fda84d6393_1 (multiqc=1.35=pyhdfd78af_0), but I would like to force rebuild a new container without having to specify the conda build hash in the environment.yml file (we don't allow that in nf-core to stay platform agnostic).
I saw that there was an option for that added https://github.com/seqeralabs/wave/pull/173/changes, but it seems like it never actually was working seqeralabs/wave@621334d
We have a case where we needed a wave container for the newer conda build of multiqc-1.35 (
multiqc=1.35=pyhdfd78af_1).We already have a container for the previous build https://wave.seqera.io/view/builds/bd-cb7458fda84d6393_1 (
multiqc=1.35=pyhdfd78af_0), but I would like to force rebuild a new container without having to specify the conda build hash in theenvironment.ymlfile (we don't allow that in nf-core to stay platform agnostic).I saw that there was an option for that added https://github.com/seqeralabs/wave/pull/173/changes, but it seems like it never actually was working seqeralabs/wave@621334d