Publish to PyPI on version tag push#4
Merged
Conversation
Add a tag-triggered publish workflow and declare hotdata-runtime as a PyPI dependency so published wheels install cleanly from pypi.org.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
3 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Publish to PyPIworkflow triggered by version tags matchingv[0-9]*hotdata-runtimedependency from a git URL tohotdata-runtime>=0.1.0so PyPI installs work (local dev still uses[tool.uv.sources])Test plan
hotdata-runtimeto PyPI first (marimo depends on it)hotdata-marimo(GitHub environmentpypi)pyproject.toml, push tag (e.g.git tag v0.1.0 && git push origin v0.1.0)