A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

When updating an nf-core module, how do I get the conda lockfile required by meta.yml, e.g.
```modules/nf-core/vuegen/.conda-lock/linux_amd64-bd-9eebdec0448f6563_1.txt```
I'm able to get all the other information from:
<https://seqera.io/containers/|seqera.io/containers>

For reference, here is my <https://wave.seqera.io/view/builds/bd-0b46ade42a5009b2_1|container>. There is a conda lockfile block there but it is a format that I don't really recognise and doesn't seem to match other modules with the lockfile

`nf-core modules bump` will do everything for you (in the latest version of nf-core /tools  (4.1.0)

Forgot to mention, I'm updating the module code in the nf-core/modules repo (in a PR) not in my own pipeline (The module is <https://github.com/nf-core/modules/tree/0041db49284f44eaeba5b861acdb7d076771d244/modules/nf-core/optitype|optitype>). nf-core modules bump just returns with `module is up-to-date`

Am running the module tests in the conda env now just to see if that lockfile is in the correct format, it seems to give me no linting errors

The bump version command only works if you didn't update anything else by hand. You just give it something to point at and it works fine. Also it gives you arm64 builds, if available 