rmcp and rmcp-macros crates no longer include LICENSE (regression since 1.3.0)
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
The regression is in the package manifests of the rmcp and rmcp-macros crates, where the license-file field was removed in #746. Read those two Cargo.toml files and compare them with the 1.2.0 release, then check what cargo package --list -p rmcp includes. Done when both packages list LICENSE, without reintroducing the Cargo warning about license and license-file, and ideally when the suggested CI check is added.
Written by the indexing model from the issue text.
Description
Describe the bug
Since 1.3.0, the rmcp and rmcp-macros crates on crates.io no longer include the repository LICENSE (it was added in #657 and dropped in #746). Downstream packagers and binary distributors need that file, including the MIT notice it carries for contributions that remain MIT-licensed.
To Reproduce
curl -sSL https://static.crates.io/crates/rmcp/rmcp-3.5.1.crate | tar -tzf - | grep -i license
Prints nothing; the same command for 1.2.0 lists rmcp-1.2.0/LICENSE.
Expected behavior
Both crates include LICENSE, as 1.2.0 did.
Additional context
#746 removed license-file to silence Cargo's warning "only one of license or license-file is necessary". That field was also what put LICENSE into the published crates, so the file disappeared.
A CI step like cargo package --list -p rmcp | grep -qx LICENSE (and the same for rmcp-macros) would catch this if it happens again.
- Dominant language
- Rust
- Stars
- 4k
- Forks
- 654
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 37
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/rust-sdk
-
Streamable HTTP client: a 401 or 403 with a JSON-RPC error body and no WWW-Authenticate loses its HTTP statusPossibly taken A pull request linked to this issue is open or already merged. Openbug P2 ready for work T-security T-transport
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/rust-sdk#1339 ·
Maintainers usually reply within 3 days
-
auth: refresh_token() requests offline_access that was never granted, so refreshes fail with invalid_scopePossibly taken @jstar0 claimed this 3 days ago. Openbug P1 ready for work T-security T-transport
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
modelcontextprotocol/rust-sdk#1330 ·
Maintainers usually reply within 3 days
-
P3 question Stale T-documentation T-enhancement
Difficulty 1/5 Under an hour Newbie friendliness 86/100
modelcontextprotocol/rust-sdk#1155 · 1 comment ·
Maintainers usually reply within 3 days
-
enhancement P2 ready for work T-service
Difficulty 4/5 3-5 days Newbie friendliness 48/100
modelcontextprotocol/rust-sdk#1338 · 1 comment ·
Maintainers usually reply within 3 days
-
Non-object outputSchema and structuredContent are sent to clients that negotiated 2025-06-18 / 2025-11-25, where an object is requiredPossibly taken @Cassian433 claimed this today. Openbug P1 ready for work T-handler T-model
Difficulty 3/5 1-2 days Newbie friendliness 28/100
modelcontextprotocol/rust-sdk#1337 ·
Maintainers usually reply within 3 days
All issues in modelcontextprotocol/rust-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
akitaonrails/ai-memory#1225 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
acsandmann/rift#577 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[Bug]: rerank on the huggingface provider (TEI) always costs $0, configured input_cost_per_query is ignoredPossibly taken A pull request linked to this issue is open or already merged. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day