Publish-to-PyPI automated flow #379
Merged
+355
−2
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
hemidactylus
changed the title
cbornet
reviewed
Oct 6, 2025
| ASTRA_DB_API_ENDPOINT: ${{ secrets.ASTRA_DB_API_ENDPOINT }} | ||
| run: make test | ||
|
|
||
| # TODO restore integration tests for final |
There was a problem hiding this comment.
Comment just to not forget the TODO
There was a problem hiding this comment.
Sure :) This is to speed up testing the flow (by a lot!)
cbornet
approved these changes
Oct 6, 2025
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 PR introduces a workflow to bundle the build+publish+release steps as a Github automation.
The advantages are:
Point 3 means that once this is fully merged, finalized and tested, API keys used so far for publishing the bundle can be revoked, reaching a more controlled security stance.
NOTE
The aim of this PR is to merge a non-finalized process to main, in order to test it from the "real" branch with no actual consequence on PyPI.
Once the tests show it's working as intended, a subsequent PR would finalize the workflow, which means in particular: