In case you saw a template update PR and are waiti...
# pipeline-maintainers
m
In case you saw a template update PR and are waiting for an official release announcement: Some of your pipelines were chosen as test subjects for the new template update. Everything should work, but we always need to do some live testing to see what doesn't work. You can already try to merge it, or leave it for now, in case we need to push out a patch release.
👍 4
m
on it
m
there will be a patch release to fix the failing pipeline lint CI action
🎉 1
cattyping 1
patch release (4.0.1) is out! syncing the previously updated pipelines, before i roll it out to all
🎉 1
❤️ 3
j
Resolving conflicts salute
j
Looks good on local nf-core pipelines lint 👍 checking with CI
🎉 1
m
I found that the nf-core modules update command is much slower compared to before. and I still have this warning:
Could not find meta.yml for MULTIQC at multiqc/meta.yml
m
where do you get that error?
m
still on the createpanelrefs pipeline, when I use this command: nf-core modules update -fay
m
ah, we don't parse modules in the top level
<http://main.nf|main.nf>
will write a fix for that
m
yeah, that's what I assumed
j
Not sure if this is in the scope of the new version: the
Important! Template update for nf-core/tools v4.0.1
PR is not automatically closed after merging a second template-merge PR. I think I recall that this was a convenient automation (ref https://github.com/nf-core/hlatyping/pulls)