I have a feeling this should be 4.0.0 actually bec...
# infrastructure
m
I have a feeling this should be 4.0.0 actually because it will require strict syntax etc
💯 2
n
Strict syntax is 26.04+ 😛 so we should be fine for this version
m
according to the roadmap we are requiring it from Q2 2026 https://nf-co.re/blog/2025/nextflow_syntax_nf-core_roadmap#nf-core-syntax-adoption
n
Ah okay just keep in mind that 25.10 strict syntax doesn't work with nf-core pipelines, we will need 26.04
m
ohno2
@Phil Ewels should we then still require strict syntax in the next template update?
p
Can you elaborate @Nicolas Vannieuwkerke?
n
There are some bugs the 25.10 strict syntax parser that cause undefined behaviour in most nf-core pipelines. These have been solved in the edge versions but not in any patch of 25.10
For example, nf-test does not work for nf-core with 25.10 strict syntax since it cannot correctly fetch profiles
p
nf-test might be acceptable as that's a developer tool, not end user tool 🤔
So we could say 25.10 for users and 26.04 for devs
n
I also seem to remember some issues with the test profile parameters not overwriting default parameters correctly, which is a bigger issue. But I've not tried running nf-core pipeline using 25.10 for a while (I'm always using the edge version). @Maxime Garcia what is your experience with #C01NHS4CC91?
m
you mean params via igenomes or things like that?
n
yeah I don't remember the details anymore but if you say it's fine then I'm happy with it
m
getGenomeAttribute for example?
since I stopped using the function from the subworkflows and switched to local or nf-core-utils, no issues anymore
n
Okay fine by me then 😛
m
isn't that subworkflow fixed by now?
m
Not sure actually since I stopped using it sooo long ago
n
you mean the nf-schema subwf issue? That was a language server issue, so it's not a problem for Nextflow itself