Hello <!channel>! We just merged a major refactoring of the

pipelines download

subcommand into the

nf-core/tools

dev branch that uses a new Nextflow 25.04 feature to hopefully make pipeline downloads more maintainable and robust! 🚀 Shoutout to @Erik Danielsson and everyone else involved for their contributions on this nf core party "Why does this affect me?" There is a github workflow in the pipeline-template that tests the

pipelines download

subcommand for all nf-core pipelines when merging to main. This workflow uses the dev version of

nf-core/tools

that is now relying on nextflow 25.04 and will cause this workflow to fail for pipelines with older Nextflow versions 🚧 alert "What to do if my workflow fails?" As always: Don't Panic! nf core duck You are of course encouraged to tell us about issues with your pipeline download workflow on #CE5LG7WMB but don't have to take any action otherwise. You may voluntarily update your Nextflow version to 25.04 already time, to fix this for you. The github workflow in question will also be changed to no longer rely on the dev version of

nf-core/tools

in the future. tl;dr Changes to

pipelines download

were merged requiring Nextflow version 25.04. This effects a release workflow in all pipelines and may cause them to fail. Learn more about the changes and the potential issues in our new blog post: https://nf-co.re/blog/2025/refurbushing-the-pipeline-download