This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
Home
David Stansby edited this page May 17, 2023
·
1 revision
Welcome to the cellfinder-core wiki!
These are instructions for doing a new release of cellfinder-core
- Update CHANGELOG.md to replace "[UNRELEASED]" with the new version number and current date.
- Check that all tests are passing on GitHub actions on the
main
branch- If they're not passing, do not continue until they are fixed.
- Create a new releae through the GitHub release web interface. Below "x.y.z" should be replaced with the new version number.
- Select to create a new tag on publish, and set the tag to "x.y.z"
- Set the release title to "cellfinder-core x.y.z",
- Click "Generate release notes"
- Make sure "Set as latest release" is ticked
- Click "Publish release". This will create a tag which in turn will launch a new GitHubs actions test workflow that includes stages to build the package and upload it to PyPI.
- Check that this GitHub actions workflow succeeds.
- Check that the version has succesfully updated on the cellfinder-core PyPI page.
- Update the cellfinder-core conda-forge feedstock. If you wait a little while a pull request should be automatically opened by a conda-forge bot. Follow the instructions on that pull request, and if everything is good merge it. Be sure to:
- Update any dependencies and versions that have changed