docs(rust): point dependency examples at the published 1.0 line - #2520
Conversation
The crate has been on crates.io since 1.0.0 (2026-06-02) and is currently
1.0.11 stable, but the README still pinned `version = "0.1"` and carried a
caveat saying the crate was not published yet.
0.1.0 (2026-05-06) predates the feature rename, so it exposes `embedded-cli`
rather than `bundled-cli` / `bundled-in-process`. Copying the README's own
feature examples therefore fails to resolve:
error: failed to select a version for `github-copilot-sdk`
The bare pin does resolve, but silently to the four-month-old 0.1.0.
With `version = "1.0"` the same examples resolve to 1.0.11.
There was a problem hiding this comment.
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Pull request overview
Updates the Rust README dependency examples to target the published stable 1.0 crate line (instead of 0.1) and removes the outdated “not published yet” note so that documented feature examples resolve correctly on crates.io.
Changes:
- Bump all
github-copilot-sdkdependency examples fromversion = "0.1"/"0.1"toversion = "1.0"/"1.0". - Remove the pre-publication caveat about needing path/git dependencies.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
SteveSandersonMS
left a comment
There was a problem hiding this comment.
Approved after validating the crates.io resolution and updating the README requirements to the repository's documented compatible \1\ Cargo style.
Summary
rust/README.mdstill pinsversion = "0.1"in every dependency example and says the crate is not published yet. It has been on crates.io since1.0.0(2026-06-02); the current stable is1.0.11.0.1.0was published 2026-05-06 and predates the feature rename, so it exposesembedded-clirather thanbundled-cli/bundled-in-process. Copying the README's own feature examples fails outright:The bare
github-copilot-sdk = "0.1"does resolve, but silently to the four-month-old0.1.0, which is a pre-1.0 API.This updates the six examples to
"1.0"and drops the stale pre-publication caveat.Verification
Real resolution, not
cargo add --dry-run(which reports features "as of v1.0.0" and rejectsbundled-in-processfor that reason even when the requirement is satisfiable):cargo generate-lockfile{ version = "0.1", features = ["bundled-in-process"] }"0.1"0.1.0{ version = "1.0", features = ["bundled-in-process"] }1.0.11, 214 packages lockedFeature sets from the crates.io API confirm the cause:
0.1.0-default, derive, embedded-cli, test-support1.0.11-bundled-cli, bundled-in-process, default, derive, test-support