Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notice: versions 0.5.553-0.5.567 were yanked from PyPI and the main branch's git history was rewritten accordingly #56

Open
cthoyt opened this issue Dec 8, 2024 · 0 comments

Comments

@cthoyt
Copy link
Member

cthoyt commented Dec 8, 2024

As a follow-up from #53, the following were done:

  1. Yanked bioversions versions 0.5.553-0.5.567 from PyPI
  2. Rewrote git history on main branch to remove the many commits related to those releases, since each release has 3 commits for updating data, making the release, then bumping the version. Normally this isn't a good idea, but here, it helped better reflect what changes were taken. The other commits that happened in the meantime related to the data updates and other minor code improvements were retained
  3. New releases are coming under the v0.6.* series, which are py310+. If you need py39 compatibility, the entire 0.5.x series on PyPI should continue to work, meaning you can pin to <0.6.0 to get py39 compatibility, or a resolver should be able to handle if you don't make a pin and you have py39 in your requirements
@cthoyt cthoyt changed the title Notice: yanked versions 0.5.553-0.5.567 from PyPI and rewrote git history on main branch Notice: versions 0.5.553-0.5.567 were yanked from PyPI and the main branch's git history was rewritten accordingly Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant