chore(workers): finish stale configuration/iii-state dependency pin refresh - #459
Conversation
…efresh #456 bumped harness's own builtin-engine pins (configuration, iii-state, iii-queue, iii-cron, iii-observability, iii-stream) from ^0.19.0 to ^0.21.3, but every worker harness also depends on still declared the old ^0.19.0 range for configuration/iii-state. That diamond is unsatisfiable (^0.19.0 and ^0.21.3 don't overlap), so resolving harness's dependency graph now fails with a 422 version_conflict against iii-directory (and would hit the same wall against llm-router, session-manager, context-manager, web, provider-anthropic, and provider-openai next). Bump the same pins in all seven to ^0.21.3 so the graph is resolvable again once each is republished.
ytallo
added
the
no-ticket
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 41 skipped (no docs/).
Four for four. Nicely done. |
📝 WalkthroughWalkthroughThis change updates version constraints for the ChangesWorker Manifest Dependency Bumps
Estimated code review effort: 1 (Trivial) | ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@provider-openai/iii.worker.yaml`:
- Around line 10-11: Several remaining iii.worker.yaml manifests still pin
configuration and/or iii-state to ^0.19.0, which will keep causing
version_conflict during iii worker reinstall harness. Update the worker manifest
entries in each affected package (including provider-openai and the listed
pubsub, worktree, cron, queue, http, approval-gate, slack, state, telegram-bot,
rbac-proxy, bridge, provider-llamacpp, provider-zai, provider-xai, and
provider-openai-codex manifests) so both configuration and iii-state are aligned
to ^0.21.3, matching the other workers.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: ca6cdc9b-ab75-4634-a497-6c2c4a05a749
📒 Files selected for processing (7)
context-manager/iii.worker.yamliii-directory/iii.worker.yamlllm-router/iii.worker.yamlprovider-anthropic/iii.worker.yamlprovider-openai/iii.worker.yamlsession-manager/iii.worker.yamlweb/iii.worker.yaml
| iii-state: "^0.21.3" | ||
| llm-router: "^1.0.0" |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Search all iii.worker.yaml files for stale ^0.19.0 constraints on configuration or iii-state.
# Find all worker manifests and check for old version pins
fd -t f 'iii.worker.yaml' --exec rg -n 'configuration:\s*"?\^0\.19' {} +
fd -t f 'iii.worker.yaml' --exec rg -n 'iii-state:\s*"?\^0\.19' {} +Repository: iii-hq/workers
Length of output: 5177
Update the remaining worker manifests to ^0.21.3. Several iii.worker.yaml files still pin configuration and/or iii-state to ^0.19.0, so iii worker reinstall harness will still hit version_conflict for those workers: pubsub/iii.worker.yaml, worktree/iii.worker.yaml, cron/iii.worker.yaml, queue/iii.worker.yaml, http/iii.worker.yaml, approval-gate/iii.worker.yaml, slack/iii.worker.yaml, state/iii.worker.yaml, telegram-bot/iii.worker.yaml, rbac-proxy/iii.worker.yaml, bridge/iii.worker.yaml, provider-llamacpp/iii.worker.yaml, provider-zai/iii.worker.yaml, provider-xai/iii.worker.yaml, provider-openai-codex/iii.worker.yaml.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@provider-openai/iii.worker.yaml` around lines 10 - 11, Several remaining
iii.worker.yaml manifests still pin configuration and/or iii-state to ^0.19.0,
which will keep causing version_conflict during iii worker reinstall harness.
Update the worker manifest entries in each affected package (including
provider-openai and the listed pubsub, worktree, cron, queue, http,
approval-gate, slack, state, telegram-bot, rbac-proxy, bridge,
provider-llamacpp, provider-zai, provider-xai, and provider-openai-codex
manifests) so both configuration and iii-state are aligned to ^0.21.3, matching
the other workers.
1 participant
Summary
^0.19.0to^0.21.3, but every worker harness depends on still declared^0.19.0forconfiguration/iii-state.^0.19.0and^0.21.3don't overlap, so resolving harness's dependency graph now fails:iii worker reinstall harness→ HTTP 422version_conflict,dependency_path: harness -> iii-directory -> configuration.^0.21.3in the seven affected manifests:iii-directory,llm-router(iii-state+configuration),session-manager,context-manager,web,provider-anthropic(iii-state),provider-openai(iii-state).Test plan
git diffscoped to exactly these 7iii.worker.yamlfiles, no stray changesiii worker reinstall harnessresolves cleanly once all 7 are republishedSummary by CodeRabbit