chore(harness): declare provider workers as direct dependencies - #291
Conversation
…opic and provider-openai
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough
ChangesRouter security docs and harness wiring
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
skill-check — worker0 verified, 22 skipped (no docs/).
Four for four. Nicely done. |
Summary
harness/iii.worker.yamlto depend directly onprovider-anthropicandprovider-openai(^1.0.0) instead ofllm-router, so the harness bundle pulls in the provider workers explicitly.llm-router/README.md: clarify which router functions are agent-callable vs worker-only, and align trigger registration examples with::function IDs.Test plan
llm-routerdependency entryiii-permissions.yamlSummary by CodeRabbit
Documentation
Chores