-
Notifications
You must be signed in to change notification settings - Fork 150
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
Publish automatically to PyPI #418
Open
aaron-skydio
wants to merge
1
commit into
aaron/revup/main/sf-auto-version
Choose a base branch
from
aaron/revup/main/sf-auto-publish
base: aaron/revup/main/sf-auto-version
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Publish automatically to PyPI #418
aaron-skydio
wants to merge
1
commit into
aaron/revup/main/sf-auto-version
from
aaron/revup/main/sf-auto-publish
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
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; on each push to main we publish a dev release to TestPYPI, and 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
|
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
from
January 3, 2025 20:22
7dffc87
to
bce9c44
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
from
January 3, 2025 20:22
8bf3a3d
to
deb7a96
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
from
January 3, 2025 20:52
bce9c44
to
2a5d6a2
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
2 times, most recently
from
January 6, 2025 05:18
121ffd6
to
cc13cb8
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
from
January 6, 2025 05:18
2a5d6a2
to
537801a
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
from
January 6, 2025 05:24
cc13cb8
to
59c8582
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
2 times, most recently
from
January 6, 2025 06:19
3d957db
to
6c93c08
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
from
January 6, 2025 06:19
59c8582
to
0216aa9
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
from
January 6, 2025 06:29
6c93c08
to
96c8faa
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
5 times, most recently
from
January 6, 2025 20:37
f5c1f46
to
5b784d6
Compare
aaron-skydio
requested review from
bradley-solliday-skydio,
nathan-skydio and
ryan-brott-skydio
and removed request for
bradley-solliday-skydio,
nathan-skydio and
ryan-brott-skydio
January 6, 2025 23:29
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-publish
branch
from
January 8, 2025 05:17
5b784d6
to
c5539e2
Compare
aaron-skydio
force-pushed
the
aaron/revup/main/sf-auto-version
branch
from
January 8, 2025 05:17
96c8faa
to
838199e
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; on
each push to main we publish a dev release to TestPYPI, and 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