Repository navigation
Fix crate keywords and add a sigit-agent README after 1.7.0 - #245
Conversation
The v1.7.0 publish of sigit failed with a 400 because the crate listed eight keywords. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The crate had no readme, so its crates.io page was empty. This one covers what the crate exports, how to serve SiGitCode in process, where the session is stored and which environment variables it reads. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
![sigit-code-review[bot]](https://avatars.githubusercontent.com/in/3492899?s=60&v=4){kind=small}
There was a problem hiding this comment.
This change fixes the crate keywords in crates/cli/Cargo.toml by reducing them from eight to five to comply with crates.io limits, aligning the development branch with the published 1.7.0 version. It also adds a new README file for the sigit-agent crate, describing its purpose, contents, usage example, session management, environment variables, and license. The sigit-agent/Cargo.toml is updated to point to this README. Review should focus on the correctness of the README content and the keyword adjustment to ensure no crates.io publishing issues remain.
Automated review by siGit Code Review · commit 3123b0b · see the review dashboard
The example calls tokio::spawn, so a reader copying it needs a tokio runtime. Say so under the snippet. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Co-Authored-By: siGit Code v1.6.9 <noreply@sigit.si>
There was a problem hiding this comment.
This change fixes the sigit crate keywords in crates/cli/Cargo.toml by reducing them from eight to five to comply with crates.io limits, aligning the development branch with the published 1.7.0 version. It also adds a detailed README for the sigit-agent crate, explaining its purpose, contents, usage example, session management, environment variables, and license. The sigit-agent crate's Cargo.toml is updated to point to this new README. Review should focus on the correctness of the README content, the example's dependency on tokio, and the keyword adjustment's impact on discoverability.
Automated review by siGit Code Review · commit ca20bf7 · see the review dashboard
3 participants
Follow-ups to the 1.7.0 release.
sigitcrate keywords from eight to five. crates.io rejects more than five, which failed the tag-triggered publish ofsigit1.7.0. 1.7.0 was published by hand from this commit, so this bringsdevelopmentin line with what shipped.sigit-agentand pointsreadmeat it. The crate had none, so its crates.io page was empty. It covers what the crate exports, servingSiGitCodein process, where the session lives and the environment variables it reads.The README only shows on crates.io with the next published version, since 1.7.0 can't be changed.
cargo fmt -- --check,cargo clippy --tests -- -D warningsandcargo test --locked -p sigit-agentpass locally.