You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did all automated tests and the Docker build in this repo pass in CI? You may have to wait for the docker image to build. Check Github actions before proceeding to the next step.
Test the new docker build in scpca-nf
Create a branch in scpca-nf for testing the latest Docker version from the main branch.
Update containers.config with the edge version of the scpca-tools container: SCPCATOOLS_CONTAINER = 'ghcr.io/alexslemonade/scpca-tools:edge' and push the branch to github.
If necessary, update the scpca-nf workflow to accommodate changes in the scpcaTools package
Perform a test run of the workflow with: nextflow run AlexsLemonade/scpca-nf -r "<TESTBRANCH>" -profile batch,ccdl
If the [default run_ids](https://github.com/AlexsLemonade/scpca-nf/blob/main/config/profile_ccdl.config#L12-L13 for the workflow do not cover expected changes in this tools package, you may want to specify particular test samples or projects with the --run_id option (use your judgement).
In Choose a tag, type a new release number using semantic versioning (vX.X.X) (you did update the title of this issue to match, right?), then click Create a new tag: vX.X.X on publish.
Write a description of the major changes in this release. You may want to start with the Auto-generated release notes to save time.
Save a draft to return to later if testing isn't done yet, otherwise:
Publish the release!
The text was updated successfully, but these errors were encountered:
This release should be just the docker update... do we want it as
0.4.1
or something like0.4.0a
, I wonder, if there are no code changes?Update, there was a code change to fix how we handle unset seeds, so 0.4.1 will be the release!
Steps for a new release of
scpcaTools
Preparing for the release and testing
scpca-nf
main
branch.edge
version of the scpca-tools container:SCPCATOOLS_CONTAINER = 'ghcr.io/alexslemonade/scpca-tools:edge'
and push the branch to github.scpca-nf
workflow to accommodate changes in thescpcaTools
packagenextflow run AlexsLemonade/scpca-nf -r "<TESTBRANCH>" -profile batch,ccdl
If the [default
run_ids
](https://github.com/AlexsLemonade/scpca-nf/blob/main/config/profile_ccdl.config#L12-L13 for the workflow do not cover expected changes in this tools package, you may want to specify particular test samples or projects with the--run_id
option (use your judgement).Creating a release
Draft a new release
.Choose a tag
, type a new release number using semantic versioning (vX.X.X) (you did update the title of this issue to match, right?), then clickCreate a new tag: vX.X.X on publish
.The text was updated successfully, but these errors were encountered: