chore: remediate Rust dependency advisories

[AnthonyRonning]

Summary

• bump the exact Diesel dependency from 2.2.3 to 2.3.10 and refresh its required macro dependencies
• refresh transitive anyhow from 1.0.100 to 1.0.103
• move transitive spin from yanked 0.9.8 to compatible non-yanked 0.9.9 without changing Axum or Multer

Security scope

RUSTSEC-2026-0136 affects Diesel's PostgreSQL CopyFromQuery / CopyToQuery option handling. OpenSecret does not use either API (or raw COPY FROM / COPY TO), so the vulnerable path was not reachable; removing the vulnerable Diesel version is defense in depth.

RUSTSEC-2026-0172 is SQLite-only. OpenSecret enables the PostgreSQL backend, not SQLite, but Diesel 2.3.10 also removes that advisory version from the lockfile.

A current cargo-audit scan reports zero vulnerabilities. It separately reports six pre-existing unmaintained-crate notices (backoff, dotenv, instant, proc-macro-error2, rustls-pemfile, and serde_cbor); those maintenance migrations are intentionally outside this focused PR.

Validation

• nix develop -c cargo fmt --all -- --check
• nix develop -c cargo clippy --all-targets --all-features --locked -- -D warnings
• nix develop -c cargo test --all-targets --all-features --locked (213 passed, 16 ignored; ignored tests require disposable Postgres)
• cargo-audit 0.22.1 against a freshly fetched RustSec advisory database (0 vulnerabilities, 6 allowed unmaintained warnings)
• cargo-deny 0.19.9 check advisories (no vulnerable or yanked packages; only the same six default-denied unmaintained notices)

---

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7a29cc63-678d-4f54-8c76-0d7faabc147e

📥 Commits

Reviewing files that changed from the base of the PR and between a3ecc93 and 3f927b7.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex-opensecret-diesel-remediation-opensecret

---

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.