Hi <!channel> 🚨 With the next major release of Nextflow comes strict syntax, which will cause pipelines to fail if the code is not compliant. We got you covered, but we need your help for the configs repo (https://github.com/nf-core/configs). 📣 Please check ALL institutional configs you use (whether within nf-core/configs, or in your own custom repositories) and see if they will still work with the new syntax parser! 👀 To help you do this, @James Fellows Yates and I wrote a blog post to hopefully make testing and fixing your configs super easy. You can find the blog post here: https://nf-co.re/blog/2026/configs-strict-syntax ⚠️ All configs in the nf-core configs repository that are not strict syntax compatible by the release of the next major Nextflow version will be marked as deprecated, meaning these configs are not guaranteed to work with all pipelines from that moment on. ⚠️ Feel free to come ask us for help or to have a chat about configs in #CGRTMASKY.

Tracking issue: https://github.com/nf-core/configs/issues/1020

I see our config is failing even through I thought I fixed it... Is there an output somewhere that catalogues the errors for each failing config?

@Nicolas Vannieuwkerke did you keep that info?

I just ran

nextflow lint

on the whole repo

Running the suggested test also gives no errors

Where is it failing?

It's listed in the "failing" list Phil just posted

Ohj it might just not be ticked off 🙂

Ah I need to update that list 😁

It does have a warning though...

~/P/test ❱ NXF_VER=26.02.0-edge nextflow lint nextflow.config                                        (base) 
Warn  nextflow.config:73:34: Parameter was not used -- prefix with `_` to suppress warning
│  73 |     } catch (java.io.IOException e) {
╰     |                                  ^

under the carpet

Aha, then that should be fixed first 😁

it's only a warn 😉

It's an easy fix 😛

Yep 🥲

I updated the list 😛