Repository navigation
Release 1.4.0 - #50
Conversation
Minor release: ed-acp-tauri gains the external stdio agent and the ed-claude crate is new. The release skill now lists both crates in the pin list and explains how to publish a new crate's first version. 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.
Release bump from 1.3.5 to 1.4.0: the workspace version and all eight internal dependency pins move together in Cargo.toml, and the release skill's pin list gains ed-acp-tauri and ed-claude plus a new section documenting how to bootstrap a brand-new crate onto crates.io (hand-publish a placeholder 0.0.1 with a short-lived publish-new token, then attach the GitHub trusted publisher so the tag publishes the real version via OIDC). The pin list in SKILL.md now matches the workspace's internal dependency set exactly, and the note that a caret requirement like "1.4" can never resolve to the 0.0.1 placeholder is correct. Nothing in the diff changes runtime code; the described dry-run behavior (per-crate "publish failed" logs with a successful exit while siblings are absent from the registry) is consistent with how cargo workspaces publish reports ordering-dependent dry runs.
Automated review by siGit Code Review · commit b6a8a72 · see the review dashboard
Bumps the workspace from 1.3.5 to 1.4.0. It is a minor release because both changes since 1.3.5 add API:
ExternalConfigandAgentState::externalined-acp-tauri(#48), and the newed-claudecrate (#49).The release skill now lists
ed-acp-taurianded-claudein its pin list and has a short section on publishing a new crate's first version.ed-claudehad no version on crates.io, so a placeholder 0.0.1 was published by hand and the GitHub trusted publisher was added forrelease-sdk-rust.yml. The v1.4.0 tag should publish the real crate through OIDC. If that publisher is misconfigured, theed-claudestep of the first run is where it will show.Checked locally:
cargo check,cargo fmt --check,cargo test --locked, andcargo clippy -D warningson the whole workspace all pass. Thecargo workspaces publish --dry-runlogs "publish failed" for crates whose 1.4.0 siblings are not on the registry yet, but exits successfully.