Merging template 4.0.3 - #453
Conversation
Merges the nf-core-bot template branch (nf-core#449, c26ac89) following the pattern used for 4.0.2 in nf-core#443: merge into a branch off dev and resolve there, rather than pushing to the bot's template branch. Only ro-crate-metadata.json conflicted. It is wholly regenerated on each build -- none of the six UUID @ids are shared between the two sides, and each is both a definition and a cross-reference -- so resolving it hunk-by-hunk risks references pointing at nodes taken from the other side. Taking the template side wholesale is also wrong: the bot generates its RO-Crate from the template README, so its description is boilerplate carrying "TODO nf-core" placeholders (7,179 chars against the real 13,620). Resolved by taking dev's file and regenerating with `nf-core pipelines rocrate`. Verified: description is the real pipeline documentation, 36 nodes, all 6 UUID references resolve, no dangling ids. .nf-core.yml and README.md auto-merged correctly, keeping the pipeline's lint configuration and real documentation while taking nf_core_version 4.0.3.
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 4.0.3. For more documentation on how to update your pipeline, please see the Synchronisation documentation. |
|
Kevin-Brockers
left a comment
There was a problem hiding this comment.
Please update also update the changelog.
Otherwise looks good!
Also fix the nf-core#443 entry, which linked to nf-core/chipseq instead of nf-core/atacseq. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
done! Also noticed there was a reference to Chipseq, which I think is a mistake, in the Changelog for PR 443, so I updated that. |
❌ nf-test failed with latest Nextflow versionNote Tests with Nextflow's latest version failed but it will not cause a CI workflow failure.
See the full run for details. |
Supersedes #449 — resolves the ro-crate conflict per the PR #443 pattern
PR checklist
nf-core lint).nextflow run . -profile test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).