chore: depend on the released SDK and orchestrator - #70
Merged
Conversation
livepeer-gateway 1.0.0 is on PyPI, so the git pins go away: pyproject asks for >=1.0.0, the [tool.uv.sources] blocks are gone, and the Dockerfiles no longer install git just to clone the SDK. go-livepeer v0.9.1 carries the session-scoped payment URL (#4008) that kept compose on a master build, so the orchestrator moves to the release tag. The previous pin is an ancestor of v0.9.1, so this is strictly newer. Verified: uv resolves 1.0.0 from the registry, hello-world builds with --no-cache and no git layer, and both the single-shot and trickle paths run end to end against v0.9.1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Both dependencies have shipped, so the git and master pins can go.
Closes #65. Closes #55.
What changes
SDK, now on PyPI as
livepeer-gateway1.0.0:pyproject.tomlasks forlivepeer-gateway>=1.0.0and the[tool.uv.sources]git blocks are deletedapt-get install gitsince that existed only to clone the SDKpip install git+...command; every example README drops "the not-yet-released SDK"Orchestrator, now
livepeer/go-livepeer:v0.9.1:compose ran a master build because metered pricing needed the session-scoped payment URL added after v0.9.0 (#4008). v0.9.1 carries it (
8229b177), and the oldsha-cc49228pin is an ancestor of the tag, so this is strictly newer rather than a downgrade. The README note explaining the master build is replaced, and the two per-example notes about needing a newer orchestrator now point at v0.9.1.Verified
uv lockfrom scratch resolveslivepeer-gateway 1.0.0fromregistry = "https://pypi.org/simple", not a git sourcedocker build --no-cachesucceeds with no git layer in the imagehello-worldend to end against the v0.9.1 orchestrator:{'message': 'Hello, PyPI!'}echo --mode robotend to end on the same stack: trickle in and out, output carriesh264+opusNote
uv.lockis gitignored, so anyone with a working tree needsuv syncto pick up the registry version instead of their cached git checkout.