Hi folks! Remember that blog post we did about adopting new Nextflow syntax? Well, 2026 is the year of actually doing all these changes 💪🏻 🚀 nextflow It'll be worth it, I promise! First up was using topics in modules, which had a big effort during the Nextflow Summit Barcelona hackathon and is making great progress 🎉 (see #C09LJTQQ3EY) Second is making all pipelines compatible with the new Nextflow "strict syntax". This is backwards compatible across versions, but getting a green tick mark for it now means that your pipeline won't break when new Nextflow versions are released and the Nextflow v2 syntax parser becomes the default (v. likely in 26.04). To help with meeting this goal, I put together a little helper repo: https://github.com/nf-core/strict-syntax-health • Runs twice a day to keep stats of how many pipelines, subworkflows and modules are passing

nextflow lint

• Keeps copies of lint results, so you can click straight through to your pipeline without running anything The good news is that ~94% of both #CJRH30T6V and #C03D38JNFNJ are already passing 🎉 The less good news is that only 12% of pipelines are passing 🫠 So - please go see if your favourite pipeline is on the naughty or nice list, and let's see if we can get green ticks across the board in the coming weeks! ✅✅✅✅🎉 catjam neon cat spin nextflow shake ▶️ https://github.com/nf-core/strict-syntax-health ◀️ nextflow pet

Curious, does this check the main or dev branch of the pipelines?

It checks

dev

(if present)

Thanks! Better, to be sure before a release