chore(harness): declare engine-worker deps - #123
Conversation
Add iii-state, iii-queue, iii-stream, iii-bridge to harness's dependency
list so a fresh `iii worker add harness` brings them up automatically.
Bump skills minimum to 0.2.4 (already shipped) to match runtime needs.
Without these, harness's bundled deps fail at boot:
- auth-credentials, session-tree, approval-gate need state::* (iii-state)
- several workers register durable:subscriber triggers (iii-queue)
- iii-stream / iii-bridge are required for the streaming/bridge paths
the harness web surface uses
Verified each engine worker resolves under ^0.11.0:
iii-state → 0.11.5
iii-queue → 0.11.4
iii-stream → 0.11.6
iii-bridge → 0.11.5
iii-http intentionally NOT added: registry has no `latest` tag for it
(only pre-releases), so depending on it would break resolution. Until
iii-http gets a stable tag, consumers can add it manually with
`iii worker add iii-http` after installing harness if they need HTTP
triggers.
|
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 (1)
📝 WalkthroughWalkthroughThe ChangesDependency Version Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 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 — worker6 verified, 20 skipped (no docs/). 82 errors across the verified workers.
|
|
Landed directly on main via d12e856 as part of the harness v0.1.4 coordinated release. |
Summary
iii-state,iii-queue,iii-stream,iii-bridgetoharness/iii.worker.yamldependencies.skillsminimum from^0.2.0to^0.2.4(latest tagged version).Why
Local install of
harness@0.1.2came up with the 15 bundled binary workers, butauth-credentials,session-tree, andapproval-gateneedstate::*functions for persistence, and a few workers registerdurable:subscribertriggers that requireiii-queue. Without those engine workers in deps, half the bundle fails at boot.Reproduction:
After this change, a fresh
iii worker add harnessbrings up all engine workers automatically.Resolution verified
Each new dep resolves under
^0.11.0:Why iii-http is NOT included
iii-httpexists in the registry (versions0.11.7-next.1,0.11.6-next.6, etc.) but has nolatesttag, so/resolvereturnsversion_not_foundfor any range. Adding it would breakiii worker add harnessfor every consumer.Followup once iii-http gets a stable tagged release: include it here so HTTP-trigger features work out of the box. Until then,
iii worker add iii-httppost-install is the workaround.Release plan after merge
Tag
harness/v0.1.4(next patch) →release-harness-bundle.ymlfans out, deps republish at 0.1.4 via the coordinated-version path landed in #121.Test plan
POST /resolvewith^0.11.0iii worker add harness+iii worker add iii-state iii-queue iii-httpbrings up all 18 workers without errorsSummary by CodeRabbit