Skip to content

ci: publish to PyPi on new release, fixes #141 #147

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

abhidg
Copy link
Contributor

@abhidg abhidg commented Jun 8, 2025

No description provided.

Copy link
Member

@sadielbartholomew sadielbartholomew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By eyeball, looks to configure the dedicated publish external workflow correctly for our context and the YAML is all valid so nothing strikes me as amiss, however I don't know a good way to test it explicitly without changing it around too much to use TestPyPI - don't want to accidentally create a new official release from a test/fork branch!

Happy to approve regardless but for validation/reassurance it would be good to know it has been tested - have you checked this via publishing to TestPyPI or otherwise?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants