Fix: Update publish pypi workflow to use hatch #108
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
lwasser
commented
Feb 25, 2024
| @@ -45,6 +44,7 @@ jobs: | |||
| if: github.event_name == 'push' | |||
| uses: pypa/gh-action-pypi-publish@release/v1 | |||
| with: | |||
| # Haven't setup trusted workflow on test pypi yet | |||
There was a problem hiding this comment.
The weird part here is i'm not sure whether we want to use hatch publish vs just the pypi publish workflow which is easy and i've used before.
There was a problem hiding this comment.
I think it is fine to keep pypa/gh-action-pypi-publish
There was a problem hiding this comment.
Using hatch to build the wheel and sdist
|
merging. we can see if it goes to testpypi |
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 closes #100 #82
NOTE: i haven't set this up before with hatch but because hatch is using setuptools_scm i suspect it's the same workflow. let's see how this runs.