chore: bump engine worker deps to ^0.20.0 (manifest sweep) - #347
Conversation
The 0.20 engine ships iii-state/iii-queue/iii-cron/configuration/ iii-observability/iii-stream at 0.20.0; the worker manifests still pinned ^0.19.0 (caret on 0.x excludes 0.20.x). Bump those runtime deps to ^0.20.0 and patch-bump each affected worker.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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, 27 skipped (no docs/).
Four for four. Nicely done. |
….3) (#366) iii worker add slack failed with a registry version_conflict: slack -> harness -> iii-state: no version satisfies ^0.20.0 and ^0.19.0 slack pinned configuration/iii-state at ^0.20.0, but the live ecosystem (harness graph) still pins ^0.19.0, so the ranges do not intersect. The ^0.20.0 bump only lands with the open dep sweep (#347); until it publishes, match the live ecosystem like telegram-bot. Patch bump to republish.
The 0.20 engine ships iii-state/iii-queue/iii-cron/configuration/iii-observability/iii-stream at 0.20.0, but 9 already-merged worker manifests still pinned these runtime deps at
^0.19.0(caret on 0.x excludes 0.20.x). Bump to^0.20.0and patch-bump each worker: web 1.1.5, context-manager 1.0.3, session-manager 1.0.3, approval-gate 1.0.4, telegram-bot 0.2.3, llm-router 1.0.3, provider-anthropic 1.0.3, provider-openai 1.0.3, iii-directory 1.0.2. Cargo.lock refreshed; --locked builds pass.