Add Automation of Python SDK Release Process. #168
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…oject toml to fix wheel metadata and remove the need of version.py and replace with txt. Update scripts along with the change from .py to .txt
…ho owns the commit
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will automate our python wheel building and publishing to PyPi to a GitHub action. This action will run when the RC branches are merged. This has been tested on the fork of my branch here.
I kept the build-wheels.sh script as fallback incase the action ever breaks and we need to run it manually.
Our Python SDK will now only support MacOS 12 or greater due to some swift compatibility issues with our Rust Core.
To get this to work, we need to add a GPG key that has a valid user and email address with a passphrase which will be added into the Secrets of this repo.
On the Test RC MR below, you will see that the pipeline had the option to add release notes. I opted to remove that as GitHub's workflow manual job doesn't accept multiline strings whether its in the workflow dispatch or we grab it from the comments its a lot of workarounds and will make it messy. I feel like it will be easier to manually commit release notes.
The nice thing is the prep and release SDK flow can be incorprated into the Go SDK as well as the JS SDK.
Heres the MOmarMiraj#41 that I have on my fork which runs through this whole flow.
These are the specific jobs:
Prep the SDKs - https://github.com/MOmarMiraj/onepassword-sdk-python/actions/runs/14250538232
Release the SDKs on GitHub: https://github.com/MOmarMiraj/onepassword-sdk-python/actions/runs/14250560322"
Wheel Builder and Publisher to TestPyPi - https://github.com/MOmarMiraj/onepassword-sdk-python/actions/runs/14250577506