Modules yaml schemes don't follow nf-core releases #3668
Description
Have you checked the docs?
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.
System information
nextflow : 24.10.5
OS : Ubuntu 24.04
nf-core : 3.3.1