search

umccr / umccrise

:snake: DRAGEN Tumor/Normal workflow post-processing
https://umccr.github.io/umccrise/
MIT License
22 stars 8 forks source link

Pin pandoc and update MultiQC #86

Closed pdiakumis closed 2 years ago

pdiakumis commented 2 years ago

Solves #84 and #85.

scwatts commented 2 years ago

Noticed the merge target is bcbio_v1.2.4 - another branch or branch name might be more appropriate here. Perhaps using bcbio as branch name and then tagging with bcbio_v1.2.4 or bcbio_v1.2.5 etc is more suitable.

Changing tagging format as above may require adjustments to the codebuild stack as it probably violates semver. Other tagging schemes could be used in place, depending if we chose that route.

pdiakumis commented 2 years ago

Don't think branch name/tag really matters in this case - we're not planning on updating the AWS production release. This is mainly for testing on Gadi, which will become obsolete soon. Let me merge this and then I'll rename the branch to bcbio and bump the version to 1.2.5.

scwatts commented 2 years ago

Renaming the branch but retaining version tag format helps cleans things up sufficiently I think.