Validate Declared Minimum Dependency Versions

TEST-VALIDATE-DECLARED-MINIMUM-DEPENDENCY-VERSIONS

Summary

Check that declared minimum dependency versions still build the supported behavior. Lockfile tests can hide newer API usage, so use targeted minimal-version checks when needed.

Rule

Validate declared minimum dependency versions.

Why

Cargo manifests communicate the minimum compatible versions a downstream project may resolve. If the crate uses APIs introduced after the declared minimum, users with minimal resolution fail even though normal lockfile tests pass.

Helps

Keeps dependency requirements honest and protects downstream minimal-version builds.

Limits

Minimal-version checks can be slow or affected by transitive ecosystem issues. Use --direct or targeted checks when the direct dependency floor is the relevant contract.

Agent Instruction

Validate declared minimum dependency versions because cargo manifests communicate the minimum
compatible versions a downstream project may resolve.

Mechanisms

Supported by cargo minimal-versions check --direct, direct minimal-resolution jobs, manifest review, dependency automation configured with increase-if-necessary, and lockfile-only update PRs.