-
Notifications
You must be signed in to change notification settings - Fork 78
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
Fix release script, derive current version from pypi #1393
Conversation
36b45ec
to
33a1624
Compare
@@ -25,9 +25,15 @@ jobs: | |||
run: | | |||
curl -sSL https://install.python-poetry.org | python3 - | |||
|
|||
- name: Get current Truss version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should fetch the latest stable release (ignores rcs), regardless of yank status which is actually what we want. Therefore, it should be safe to rely on this as the current version number to bump from.
bin/bump_truss_version.sh
Outdated
# ./bump_version.sh minor # bumps the minor version (resets patch to 0) | ||
# ./bump_version.sh 0.9.60 # bumps the patch (micro) version by default | ||
# ./bump_version.sh 0.9.60 major # bumps the major version (resets minor and patch to 0) | ||
# ./bump_version.sh 0.9.60 minor # bumps the minor version (resets patch to 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Add expected new versions, just to be explicit.
🚀 What
My recent attempt to improve the release flow had a slight bug which caused us to skip a version number. The root cause is we create RCs off the next intended version, which my script didn't account for. Instead of trying to bake that logic into the script, I actually think it's better to derive the current version from PyPI rather than try to parse it from
pyproject.toml
💻 How
🔬 Testing
Created #1394