chore: automate package publishing process with uv #40
Conversation
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
jeduardo
changed the title
1. test.yaml: run tests (all PRs and main on merge) 2. release.yaml: calls release-please to decide whether to cut a new release 3. publish.yaml: publishes package to PyPI and docs to github pages
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.
Shifting project management to
uvfor this one as it makes it easier to produce and publish the release packages and also to test the code with different Python versions.This PR revamps the Makefile interface to leverage
uvand restructures the release process onto distinct phases for testing/release-management/publishing.Note: most of the code was reformatted to comply with new formatting/linting rules.