What we see • With default plugins, the pipeline fetches nf-schema@2.5.1 and fails pre-launch due to NF version:

Failed requirement - Plugin nf-schema@2.5.1 requires Nextflow version >=25.04.0 (current 24.10.9)

• If we pin the plugin to 2.4.2:

plugins {
  id 'nf-schema@2.4.2'
}

• the workflow launches but compiles fail under NF 24.10.9 with duplicate var errors in modules/local/prelude/main.nf:

Variable `output_file_xml` already defined...
Variable `output_file_markersheet` already defined...
Variable `output_file_samplesheet` already defined...
Variable `output_file_markersheet` already defined...

Repro notes • Local with NF 24.10.9 + nf-schema@2.4.2 → same duplicate variable errors. • Local with NF 25.10.0 + nf-schema@2.4.2 → compiles and runs through PRELUDE; later steps run (i.e., the immediate blocker is NF version / compile under 24.10.9). Request 1. Given we’re stuck on NF 24.10.9 in SqP for now would you accept a small PR that removes the duplicate variable declarations in modules/local/prelude/main.nf so it’s backward-compatible with 24.10.x when nf-schema is pinned to 2.4.2?

FYI @Jeremy Muhlich

I opened a PR that seems to fix it but appreciate testing https://github.com/nf-core/mcmicro/pull/122