fix(deps): resolve audit advisories and update all dependencies to latest - #62
Merged
Conversation
testcontainers 0.27.1 pulled astral-tokio-tar 0.5.6, affected by RUSTSEC-2026-0066/-0112/-0113/-0145 (PAX header desync, symlink chmod, insufficient PAX validation). testcontainers 0.27.3 pulls astral-tokio-tar 0.6.3, which is patched for all four. Dev-dependency only; no source changes required.
rmcp 0.8.5 is affected by RUSTSEC-2026-0189 (CVE-2026-42559): the Streamable HTTP server transport did not validate the Host header, enabling DNS-rebinding attacks against locally running servers. Fixed in rmcp >= 1.4.0; upgrade to the latest 2.1.0. rmcp 2.x is a breaking change; migrate the affected API usage: - model::Content -> model::ContentBlock (as_text() moved onto the enum; drop the removed .raw wrapper in the test helper). - ServerInfo (InitializeResult) and Implementation are now #[non_exhaustive]; build them from Default plus Implementation::new() and the with_website_url builder instead of struct literals. - #[tool_handler] now defaults to Self::tool_router() (rebuilt per request); pin it to the cached field via #[tool_handler(router = self.tool_router)] to preserve build-once. StreamableHttpServerConfig::default() now enforces loopback-only Host validation (the DNS-rebinding fix), which our transport picks up via Default::default().
Routine cargo update: anyhow, clap, futures, hyper, hyper-util, log, once_cell, regex, serde_json, tempfile, tokio, tower, html2text and their transitive dependencies to the latest compatible versions. Lock file only; no manifest or source changes.
Our tools declared schemars 0.8 while rmcp 2.1.0 requires schemars 1.0, leaving three schemars versions (0.8, 0.9, 1.1) in the tree. Bump our dependency to 1.x so the whole tree resolves to a single schemars 1.2.1. Derive-only usage; no source changes required.
AzureError uses the standard derive(Error) + #[error]/#[from] pattern, which is source-compatible with thiserror 2. No code changes required.
Only usage is env_logger::init() in main(), which is unchanged across the 0.11 release. No code changes required.
MockAzureDevOpsApi via #[automock] and the expect_*/returning test API are source-compatible with mockall 0.15. Integration tests pass.
The single from_read(bytes, width) -> Result call in simplify_work_item_json is unchanged across 0.17. Simplification tests pass, HTML-to-text output unchanged.
install.rs uses toml::Value, from_str, to_string_pretty and map::Map, all retained in toml 1.x. Codex config round-trip tests pass.
dotenv 0.15 was declared but never referenced in any source or test. It is unmaintained (RUSTSEC-2021-0141); removing it drops the advisory warning and a dead dependency from the tree.
Our HTTP client uses the stable surface (Client, Method, header(), json(), send(), text(), bytes(), bearer_auth(), header::HeaderMap), all source-compatible with reqwest 0.13. Retains rustls-free native-tls with json + multipart features.
azure_identity 1.0 removed DefaultAzureCredential. Replace it with an ordered fallback chain that preserves the previous behavior: managed identity first (production / Azure-hosted deployments), then Azure CLI and Azure Developer CLI (local development). Sources that fail to initialize are skipped so the remaining ones stay usable. Migrate to the 1.0 API surface: TokenCredential moved to azure_core::credentials; get_token now takes a scopes slice plus options and returns AccessToken; token.token.secret() unchanged. Add a unit test asserting the chain always exposes at least one source.
Update the dependency version tables (rmcp 2.1.0, reqwest 0.13, azure 1.0, thiserror 2, schemars 1, env_logger 0.11, mockall 0.15, html2text 0.17, toml 1, testcontainers 0.27.3; remove dotenv) and replace all DefaultAzureCredential references with the new managed identity -> Azure CLI -> Azure Developer CLI credential chain, including the architecture diagrams.
azure_identity 1.0 removed DefaultAzureCredential; update the project and MCP tooling rules to describe the managed identity -> Azure CLI -> Azure Developer CLI credential chain that replaced it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves all outstanding
cargo auditfindings and brings every dependency to its latest version.cargo auditnow exits clean (0 vulnerabilities); the tree shrank 416 → 382 crates as duplicate/unused deps were collapsed.Security fixes (were failing CI
Security Audit)astral-tokio-tar0.5.6testcontainers0.27.1 → 0.27.3 (pullsastral-tokio-tar0.6.3)rmcp0.8.5rmcp→ 2.1.0 (loopback-onlyHostvalidation on by default)dotenvDependency upgrades
cargo update): anyhow, clap, futures, hyper, hyper-util, log, once_cell, regex, serde_json, tempfile, tokio, tower, and transitives.schemars0.8 → 1 (aligns with rmcp, removes 3-way duplication) ·thiserror1 → 2 ·env_logger0.10 → 0.11 ·mockall0.12 → 0.15 ·html2text0.16 → 0.17 ·toml0.8 → 1 ·reqwest0.11 → 0.13.rmcp 0.8.5 → 2.1.0 (breaking)
model::Content→model::ContentBlock(as_text()moved onto the enum; dropped the removed.rawwrapper).ServerInfo/Implementationare now#[non_exhaustive]; built fromDefault+Implementation::new().with_website_url().#[tool_handler(router = self.tool_router)]pins the cached router (2.x defaults to rebuilding per request).azure_core / azure_identity 0.17 → 1.0 (breaking, auth)
azure_identity 1.0 removed
DefaultAzureCredential. Replaced with an explicit ordered fallback chain that preserves the previous behavior:Sources that fail to initialize are skipped. Migrated to the 1.0 API (
TokenCredentialmoved toazure_core::credentials;get_tokentakes a scopes slice + options and returnsAccessToken). Added a unit test asserting the chain always exposes at least one source.Docs
Updated
docs/PROJECT.md,docs/ARCHITECTURE.md(incl. mermaid diagrams, validated withmmdc) and the.claude/rulesauth invariant to describe the new credential chain and the upgraded dependency versions.Verification
cargo fmt --check,cargo clippy --features test-support -- -D warnings: cleancargo test --features test-support: 163 tests pass across 13 binariescargo build --release: cleancargo audit: exit 0, 0 vulnerabilitiesinitializehandshake returns correctserverInfo/capabilities; binary starts and builds the credential chain without panic.Note
The rmcp DNS-rebinding fix enables loopback-only
Hostvalidation by default. A--serverdeployment reached via a non-loopback hostname (e.g. behind a reverse proxy) will need its allowed hosts configured; a follow-up--allowed-hostCLI flag is the intended path if that use case is needed.