Create workflows to build and publish to PyPI#498
Merged
BrianJKoopman merged 3 commits intomasterfrom Feb 5, 2026
Merged
Conversation
iparask
reviewed
Feb 4, 2026
iparask
reviewed
Feb 4, 2026
iparask
reviewed
Feb 4, 2026
iparask
reviewed
Feb 4, 2026
iparask
approved these changes
Feb 5, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 should wrap up the packaging efforts for now, publishing to PyPI on release and on push of pre-release tags for
v0.x.y, i.e.v0.6.3rc1. This is largely based on publishing workflows fromocs,so3g, andsotodlib.There's a test workflow that builds the wheel, installs, and tries to import
sodetlib. This should catch any build/installation problems before an actual release happens. This workflow only runs after a merge tomaster(not every PR, which seemed excessive.)I've tested this as best I can without actually publishing anything, so on the off chance we run into a problem with publishing it might take a couple more rapid PRs/releases to fix, but it should be fairly smooth after that.
We'll want to merge #497 before making any actual releases/testing this more.