-
Notifications
You must be signed in to change notification settings - Fork 163
Publish automatically to PyPI #418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
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
Member
Author
|
Reviews in this chain: |
Member
Author
|
7dffc87 to
bce9c44
Compare
8bf3a3d to
deb7a96
Compare
bce9c44 to
2a5d6a2
Compare
121ffd6 to
cc13cb8
Compare
2a5d6a2 to
537801a
Compare
cc13cb8 to
59c8582
Compare
3d957db to
6c93c08
Compare
59c8582 to
0216aa9
Compare
6c93c08 to
96c8faa
Compare
f5c1f46 to
5b784d6
Compare
5b784d6 to
c5539e2
Compare
96c8faa to
838199e
Compare
04e31d2 to
42da475
Compare
42da475 to
bc482e7
Compare
Use the pypa-blessed github action to publish built wheels automatically to PyPI: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/ Just following the instructions there, with modifications to handle our three different packages. This setup is much nicer in combination with automatic versioning; when a tag is pushed (which will tell setuptools_scm that the symforce version should be that tag), wheels are published to PyPI. Topic: sf-auto-publish Relative: sf-auto-version
bc482e7 to
5f3ae20
Compare
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.
Use the pypa-blessed github action to publish built wheels automatically
to PyPI:
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
Just following the instructions there, with modifications to handle our
three different packages.
This setup is much nicer in combination with automatic versioning; when
a tag is pushed (which will tell setuptools_scm that the symforce
version should be that tag), wheels are published to PyPI.
Topic: sf-auto-publish
Relative: sf-auto-version