Felxible Dependencies

[bh2smith]

• Pin reqwest to ^0.12
  Downgrading from 0.13 avoids pulling two reqwest versions into the same build. Crates like alloy_transport_http depend on reqwest 0.12; when duners used 0.13, dependents saw type mismatches (Httpreqwest::Client vs Http<alloy_transport_http::Client>) because reqwest::Client from different major/minor versions are distinct types. Keeping duners on ^0.12 lets Cargo resolve a single reqwest version and restores compatibility with the alloy ecosystem.
• Use caret ranges and relax to minor/major where appropriate
  All dependencies now use explicit ^ and, where reasonable, minor- or major-level bounds (e.g. ^0.4, ^1.0). That (1) allows semver-compatible upgrades without changing duners, (2) improves version unification so dependents are less likely to get duplicate copies of the same crate, and (3) matches common practice (e.g. Cargo book and semver for compatibility). Patch/minor bumps within the same major are assumed safe for these libraries.

[cursor]

PR Summary

Low Risk
Only changes dependency version constraints; main risk is indirect behavior changes from resolving different transitive versions, especially around the reqwest downgrade.

Overview
Relaxes Cargo.toml dependency version constraints by switching from fully pinned versions to caret ranges (e.g., ^0.4, ^1.0) to allow semver-compatible upgrades and improve version unification for downstream crates.

Downgrades reqwest from 0.13.x to ^0.12 to avoid pulling multiple reqwest versions into dependent builds and reduce type/version conflicts in ecosystems that standardize on reqwest 0.12.

^{Written by Cursor Bugbot for commit f418399. Configure here.}