chore: prepare v0.1.1 release#7
Merged
Merged
Conversation
Remove the stale ../sdk-python editable override now that hotdata 0.2.0 is on PyPI so fresh checkouts and CI can uv sync without sibling repos.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
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
[tool.uv.sources]override that pinnedhotdatato../sdk-pythonuv.locksohotdata 0.2.0resolves from PyPIThis unblocks publishing hotdata-runtime 0.1.1, which adds managed database helpers (
list_managed_databases,create_managed_database,load_managed_table, etc.) already merged in #4.Why
The editable sdk-python pin leaked into the lockfile and breaks
uv syncfor anyone without a sibling../sdk-pythoncheckout.hotdata 0.2.0is now on PyPI, so the override is no longer needed.Test plan
uv sync --lockeduv run pytest(47 passed)After merge
v0.1.1onmain:git tag v0.1.1 && git push origin v0.1.1