Conversation
Update README.md for JOSS review
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.2.0. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
|
The "nf-core pipelines download nf-core/coproid" fails because it uses nextflow 25.10.3. The documentation has been updated to use nextflow ≤ 24.10.5. |
jfy133
left a comment
There was a problem hiding this comment.
Even though it's a tiny patch release, you're missing a CHANGELOG update!
Also @MeriamOs this should be resolved if you merge in the latest templates I would imagine. It would make a lot of sense to include this in the patch release rather than having a restrictive maximum NXF verison. |
|
And @jfy133 I'm planning to do this in the not so near future, but trying to get a paper out for JOSS. Manuscript is all ready to go just needed to get these reviewers comments incorporated, so have prioritised these changes. Aiming to get the new templates incorporated into the next patch release!
|
…roid into nf-core-template-merge-3.5.1
|
If it's published, make sure you mention it on the nf-core website :) |
…roid into nf-core-template-merge-3.5.1
…roid into nf-core-template-merge-3.5.1
…roid into nf-core-template-merge-3.5.1
|
And merging that in should update this PR too |
johnvusich
left a comment
There was a problem hiding this comment.
Happy to review the new template in the next patch release as well
Important! Template update for nf-core/tools v3.5.1
|
@johnvusich new template has been merged by the amazing @jfy133 and seems to have fixed the error described by you in #87 ! The only test that doesn't run to completion is the nf-test / conda with Nextflow version 25.04.0. Singularity and docker work with 25.04.0, and all work with the newest Nextflow. @johnvusich and @jfy133 is this still okay to merge?
|
jfy133
left a comment
There was a problem hiding this comment.
Ok, so I'm going to give this a ✅ for the purposes of getting this out for the paper, however:
-
None of the Conda tests are working actually (if you look inside the test logs it fails elsewhere, you have to look at the summary page to see the true results, long story but we are stuck with some GHA restrictions)
-
However, Conda support is only a (strong) recommendation not a requirement for nf-core (https://nf-co.re/docs/guidelines/pipelines/recommendations/bioconda)
-
The Conda issues are actually upstream problems with the Conda recipes not the pipeline itself (so would take longer to fix)
-
I also noted during my review that there is a lot of strict syntax violations and other suboptimal code that will be possible become more problematic in the future.
However given the the pipeline works with the current versions when using docker/Singularity (which is mandatory requirement) I'll allow this to merged and the release cut on the proviso that Conda and strict syntax fixes are made into issues and will be worked on in the future with high priority!
@MeriamOs please finish ALL steps of the release here: https://nf-co.re/docs/checklists/pipeline_release
And a note to the paper reviewers (on behalf of the nf-core core team), we don't like to be too restrictive with nextflow version pinning (i.e. setting a max version) as generally Nextflow Is pretty good with backwards compatibility and we don't want to see too much variation across all the pipelines in the community, which is why this pipeline only has a minimum version (which we have just bumped in the previous PR)
PR checklist
Updated README file to correct nextflow version batch and add extra information on running the pipeline offline or on HPC.
nf-core pipelines lint).nextflow run . -profile test,docker --outdir <OUTDIR>).README.mdis updated (including new tool citations and authors/contributors).Note:
The "nf-core pipelines download nf-core/coproid" fails because it uses nextflow 25.10.3. The documentation has been updated to use nextflow ≤ 24.10.5.