fix(slack): match live engine dep ranges so the worker installs (v0.1.3) - #366
Conversation
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 latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 28 skipped (no docs/).
Four for four. Nicely done. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe slack worker crate version is bumped from Slack worker version and dependency updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
✨ 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 |
Summary
iii worker add harness console slackfails at the slack step:slack pins
configuration/iii-stateat^0.20.0, but the live ecosystem (theharnessgraph) still pins^0.19.0.^0.20.0 ∩ ^0.19.0 = ∅, so the resolver rejects the install.The
^0.20.0convention only arrives with the open dependency sweep (#347); until that publishes, slack must match the live ecosystem — same astelegram-bot(^0.19.0).Change
iii.worker.yaml:configuration/iii-state→^0.19.0(harness/session-managerunchanged at^1.0.0).0.1.2→0.1.3so the registry republishes the fixed manifest.No code change. When #347 lands and sweeps the ecosystem to 0.20, slack moves with it.
Summary by CodeRabbit
0.1.3.