Closed adamltyson closed 11 months ago
@willGraham01 is there anything I've forgotten in this process following renaming a repo?
Technically we should release the final version under the old name (to PyPI), before releasing the new version under the new name (to PyPI).
Releasing the new version will require us changing the API key on the automatic deploy, and will mean we can't roll back to the old name to mark as deprecated.
The repo, it turns out, can be renamed whenever since it doesn't contribute to the metadata.
This repo doesn't have an API secret saved anyway I don't think. I'm also not a maintainer of the old PyPI package. I've asked @FedeClaudi to add me, then I can release the final version of bgheatmaps
which has a warning about the renaming. This is in a branch (https://github.com/brainglobe/brainglobe-heatmap/tree/deprecate) and can be released anytime. Considering this, I guess we can just go ahead and release the first version of brainglobe-heatmap
?
brainglobe-heatmap is now released, and the pypi key has been added to the repo for future releases.