feat: automated releasing via GitHub Actions #345
Merged
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
nwithan8
approved these changes
Jul 29, 2024
jchen293
previously approved these changes
Jul 29, 2024
nwithan8
requested changes
Jul 29, 2024
nwithan8
previously approved these changes
Jul 29, 2024
nwithan8
approved these changes
Jul 29, 2024
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.
Description
Now that we have an API Key saved to GitHub Actions for PYPI, we can use it to automate releasing this lib. Once a GitHub Release has been created (which automatically creates an accompanying tag), GitHub Actions will build and publish the library to PyPi.
Testing
I've used this workflow in ~40 other repos for the last ~3 years with 0 problems.
Pull Request Type
Please select the option(s) that are relevant to this PR.