Modules yaml schemes don't follow nf-core releases

Have you checked the docs?

• nf-core website: troubleshooting
• nf-core modules documentation

Description of the bug

When yaml schemes for modules meta.yml or environment.yml files change, they don't get tagged. It doesn't seem to affect linting through the nf-core CLI.

However, it does raise errors in IDEs that have the capabilities to validate yaml files based on it. On my end, it causes a lot of confusion from developers, which end up turning off validation as the best alternative.

Could you start tagging modules following nf-core/tools releases ? This way, we can target the correct yaml validation scheme in meta.yml files being developed, based on the version of nf-core/tools we run when developing ?

Command used and terminal output

No command to run. Problems arise in IDEs.

Relevant files

This meta is valid under nf-core 3.3.1, but since today's (07/07/2025) update to modules master, yaml validation gives errors.

meta.zip

System information

nextflow : 24.10.5
OS : Ubuntu 24.04
nf-core : 3.3.1

Start by reviewing the module meta.yml and environment.yml schema references and how nf-core/tools releases are exposed to the nf-core CLI. Compare the valid meta.zip example with the schema used by nf-core 3.3.1 and the current modules master. Done means module YAML schemes can be selected or identified by the corresponding nf-core/tools release so IDE validation uses the correct version.