fix(providers): sync deepseek and zai locks with llm-router 1.4.2 - #731
Conversation
The standalone provider lockfiles still pinned llm-router 1.4.1 after the path dependency was bumped, so every --locked build of provider-deepseek and provider-zai fails (Harness E2E Daily has been red since the bump). Regenerated with cargo metadata; no other entries changed.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The standalone provider lockfiles still pinned
llm-router 1.4.1after the path dependency was bumped to 1.4.2, so every--lockedbuild ofprovider-deepseekandprovider-zaifails with:This is what broke last night's Harness E2E Daily (run 31078732959) at the Build source E2E stack step — the daily builds
provider-$providerfor every subject/judge provider with--locked, and the current matrix is deepseek subject + zai judge.Regenerated both locks with
cargo metadata; the only change isllm-router 1.4.1 → 1.4.2in each. Verified locally:cargo metadata --lockedpasses for both, andcargo check --lockedcompiles provider-deepseek clean. Same drift class previously fixed in 8d053c2.Note: the Aug 4/5 daily failures are unrelated (
shell_coder_sandboxhard-gate failures, already being addressed onfix/harness-shell-coder-e2e-improvement).