Home

Current strategy to publish a new version:

• make a pull request from dev version to beta if needed and delete dev branch
• change version number in bin/needlestack.r to be written in the VCF (remove beta)
• change version number in needlestack.nf help and log messages (remove beta)
• change version number in bin/needlestack.sh help and log messages (remove beta)
• change version number in nextflow.config for the default docker container
• change version number in Singularity for the source docker container
• make a pull request from beta version to master and delete beta branch (unprotect it first)
• create a new release along with tag name corresponding to the new version
• create a new tag build in dockerhub corresponding to the new version tag
• create beta branch for next version and protect it
• create dev branch from beta
• change version number in deploy.sh CHANGELOG in branch dev for the next version (without the b)
• change version number in bin/needlestack.r to be written in the VCF in branch dev for the next version
• change version number in needlestack.nf help and log messages in branch dev for the next version
• change version number in nextflow.config for the default docker container in branch dev (put dev)
• make a pull request to the new beta branch with these first changes