-
Notifications
You must be signed in to change notification settings - Fork 17
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
Release sdist and wheel to PyPI under v0.2.1 #43
Comments
@matthewfeickert should also make an announcement on Issue #26 when this is done. |
@dguest The workflow that I recommend in Option 1 would explicitly be: First release
Next release
|
This is done and |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After PR #41 is in then we need to get
pandamonium
tov0.2.1
on PyPI. This is because before control was ceded to @dguest in Issue #26 of the PyPI namespace there already was av0.2.0
release of the previouspandamonium
. It is necessary to get pastv0.2.0
on PyPI so the future releases will properly support both sdists and wheels on PyPI.There are two ways to do this:
The easy way of just using the
bump2version
workflow described in PR Preferences for CD workflow to publish to PyPI #36 to release av0.2.0
to PyPI which will only successfully be able to upload av0.2.0
wheel to PyPI as there was already an sdist at the release version, and then immediately afterwards releasev0.2.1
.Apply the attached patch 0001-Bump-version-0.1.0-0.2.0.patch.txt (that GitHub made me name .txt) with
and then run
bump2version
with non-stagged changesto go from
v0.1.0
tov0.2.1
.I would advocate for option 1 as it is the easiest.
The text was updated successfully, but these errors were encountered: