-
Notifications
You must be signed in to change notification settings - Fork 10
Release procedure
John Kerl edited this page Oct 16, 2024
·
3 revisions
- Chat with other team members to see if they have anything else to go into the release
- https://pypi.org/manage/project/somacore/releases/
- You should be an admin, or, ask someone who is an admin to check for you
- https://pypi.org/manage/project/somacore/settings/ and look for "Project size"
- Make sure that isn't near 10GB (unlikely for this repo)
- If it is almost 10GB:
- Your GitHub tag will succeed but the PyPI publish will fail
- You can delete a few ancient releases as long as you're certain no one in the world depends on them
- You can poke a button in PyPI to request a quota upsize but that can take a few days
- Go to https://github.com/single-cell-data/SOMA/releases and poke 'Draft a new release'
- Choose a tag like
python-v1.0.n
wheren
is one more than the latest release- Note the
python-v
prefix, which we don't use for the TileDB-SOMA repo but which we do use for this - Make sure you've selected target =
main
- Title "Python v1.0.n" where
n
is as above - Poke the "Generate Release Notes" button
- Edit the release notes if you like -- maybe a sentence at the top summarizing the context/reason -- maybe a GitHub tracking issue, for example
- Note the
- Select 'Set as the latest release'
- Select 'Publish release'
- This is automated
- Go to https://github.com/single-cell-data/SOMA/actions
- Find the action for publish to PyPI (should already be running)
- You can click in for details
- In a few minutes, look for the latest wheel at https://pypi.org/project/somacore/#history
Please follow https://github.com/TileDB-Inc/somacore-feedstock/wiki/Release-procedure