fix CI: remove stale 'caspian' workspace ref corrupting the lock (main is red) - #199
Merged
Conversation
The caspian->caspian-sdk rename (during the 1.0 publish) left dead entries in
the root pyproject: a 'caspian' dependency and source pointing at a workspace
member that no longer exists under that name. That produced a uv.lock with two
websockets blocks, and 'uv sync' failed to parse it ('missing source field but
more than one matching package') - which is why main's Lint & Test was red.
Drop the stale refs, regenerate the lock (one websockets block now), and pin
setup-uv to 0.12.5 so a future uv version cannot reintroduce a format drift.
Verified locally: uv sync + uv sync --locked pass, ruff clean, 455 tests green
on 3.10/3.11/3.12.
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.
Main's Lint & Test has been failing on every commit. Root cause found and fixed.
The
caspian->caspian-sdkrename during the 1.0 publish left dead entries in the rootpyproject.toml: acaspiandependency and acaspian = { workspace = true }source, both pointing at a workspace member that no longer exists under that name. That corrupteduv.lockinto having twowebsocketsblocks, anduv syncfailed to parse it:Fix:
caspianrefs from the rootpyproject.toml.uv.lock(now onewebsocketsblock).setup-uvto0.12.5in both jobs so an unpinned newer uv can't reintroduce a format drift.Verified locally with the exact CI commands:
uv syncanduv sync --lockedpass,ruff check .clean, 455 tests green on 3.10 / 3.11 / 3.12.Unblocks every PR, including the upcoming MCP server.