Is it acceptable to downgrade a tool version in a ...
# modules
d
Is it acceptable to downgrade a tool version in a module? Currently I'm migrating the BUSCO module in mag to the nf-core one, and I found an issue in the latest (5.8.2) version of BUSCO (https://gitlab.com/ezlab/busco/-/issues/778), and the solution for now is to use an older version (5.8.0). The nf-core module currently uses the latest version, so I was considering opening a PR to downgrade it (with a comment explaining the issue). However, I'm unsure whether downgrading the version would be problematic.
l
I am unsure whether downgrading would be ok - Are there new important features in the latest version? it seems other pipelines are using it too Another quick alternative is to have a patch in your pipeline, where you need to run this offline mode, where you use the older container for the nf-core module of busco https://nf-co.re/docs/nf-core-tools/modules/patch But yeah, if the module then would be buggy for other pipelines too then maybe it would be better downgrading for everybody? But let's hear other people's opinion
m
Rather than patch, update the
modules.config
to override the container and leave a comment to the issue it's resolving.