This should include changes to use .h5ad extension and bug fixes from #743, #742, and #745.
Preparing for the release
[x] Are all of the issues planned for this release resolved? If there are any issues that are unresolved, mark this issue as blocked by those on ZenHub.
[x] Update code and documentation with the latest version number in the development branch:
[x] Test that the workflow is in good working order with nextflow run alexslemonade/scpca-nf -latest -r development
[x] File a PR from the development branch to the main branch. This should include all of the changes that will be associated with the next release.
[x] (Optional) Generate new example scpca-nf output files.
If updating the example output is not necessary for this release, check these boxes off for free.
[x] Compress the example output in scpca_out to create scpca_out.zip, as described in the instructions, and ensure the file is set to public and read-only.
Creating a release
[x] On the releases page, choose Draft a new release.
[x] 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.
[x] Write a description of the major changes in this release. You may want to start with the auto-generated release notes to save time.
[ ] Optional: If not all issues have been addressed, save a draft to return to later.
Steps for a new release of
scpca-nfThis should include changes to use
.h5adextension and bug fixes from #743, #742, and #745.Preparing for the release
developmentbranch:nextflow.configinternal-instructions.mdexternal-instructions.mdnextflow run alexslemonade/scpca-nf -latest -r developmentdevelopmentbranch to themainbranch. This should include all of the changes that will be associated with the next release.scpca-nfoutput files. If updating the example output is not necessary for this release, check these boxes off for free.scpca-nfworkflow and ensure it looks correct.scpca_outto createscpca_out.zip, as described in the instructions, and ensure the file is set to public and read-only.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.