Repository navigation
docs+ci: LICENSE (Apache 2.0), refreshed README, binary releases for all Rust workers - #35
Conversation
…all Rust workers - LICENSE: Apache License 2.0 at the repo root so licensing is explicit (matches the SDK + engine). - README.md: replace the two-worker todo/image-resize stub with a module table covering all 17 merged workers plus how binary releases, the registry, and CI are wired. - .github/workflows/release-rust-worker.yml: new generic release flow that fires on <worker>/v* tags for a2a, agent, coding, eval, experiment, guardrails, introspect, llm-router, mcp, and shell. Derives bin_name = iii-<worker>, reuses _rust-binary.yml for the 9-target cross-compile matrix, creates the GitHub Release, and uploads SHA-256 checksummed artifacts. - .github/workflows/create-tag.yml: expand the worker choice list to include every newly released Rust worker so /Create Tag can bump any of them. - .github/workflows/ci.yml: run cargo fmt --check, cargo clippy -D warnings, and cargo test per-worker via paths-filter + matrix for the new Rust workers (iii-lsp and iii-lsp-vscode stay on their dedicated jobs because iii-lsp still uses a git dep in CI). - registry/index.json: add binary entries for a2a, agent, coding, eval, experiment, guardrails, introspect, llm-router, mcp, shell so 'iii worker add <name>' can resolve the published release assets.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 1 minutes and 21 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ 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 |
1 participant
Summary
LICENSEat the repo root — closes the licensing gap.README.mdas a full module table covering the 17 merged workers plus build/release/registry/CI guidance.release-rust-worker.yml— new generic release workflow fora2a,agent,coding,eval,experiment,guardrails,introspect,llm-router,mcp,shell. Tag<worker>/v<X.Y.Z>ships 9-target cross-compiled binaries with SHA-256 checksums through the existing_rust-binary.yml.create-tag.ymlchoice list expanded to every newly releasable worker.ci.ymlrunscargo fmt --check+cargo clippy --all-targets -- -D warnings+cargo test --all-featuresper-worker viapaths-filter+ matrix.registry/index.jsonnow carries binary entries for all 10 new Rust workers soiii worker add <name>can resolve release assets.Per-worker bin names
image-resize and iii-lsp keep their existing dedicated release files.
Test plan
Create Tagagainst a single worker (dry-run) to verify the generic release pathregistry/index.jsonis accepted by downstreamiii worker add