Push stubs to pypi only on a release #5845
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
jepler
approved these changes
Jan 12, 2022
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.
Previously, c
ircuitpython-stubswas pushed to pypi on every merge. This generates a lot of releases in https://pypi.org/project/circuitpython-stubs/, most with strange version numbers. Instead, push stubs to pypi on when a release is done.Stubs are still built and pushed to https://adafruit-circuit-python.s3.amazonaws.com/index.html?prefix=bin/stubs/ on every merge. I just cleaned this up to include only releases, but it will repopulate quickly enough. I will add it to my monthly or so manual S3 cleanups.
I thought originally I would move this run step to
create_website_pr.yml, but this is better.