chore(deps): update rust crate serde_json to v1.0.151

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
serde_json	dependencies	patch	1.0.149 → 1.0.151

---

Release Notes

serde-rs/json (serde_json)

v1.0.151

Compare Source

• Add RawValue::from_string_unchecked (#​1331, thanks @​WonderLawrence)

v1.0.150

Compare Source

• Reject non-string enum object keys (#​1324, thanks @​puneetdixit200)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[doubleword-code]

Summary

This PR updates the serde_json dependency from v1.0.149 to v1.0.150 via a Cargo.lock version and checksum bump. After reviewing the release notes and searching the codebase for potentially affected patterns, this is a safe, low-risk dependency update.

Verdict: Ready to approve

Research notes

Fetched release notes for both versions:

• v1.0.150 (May 21, 2026): "Reject non-string enum object keys" (#1324) - This change rejects attempting to use enum variants as JSON object keys, which is already invalid JSON (JSON only permits string keys).

• v1.0.149 (Jan 6, 2025): "Align arbitrary_precision number strings with zmij's formatting" (#1306) - Internal formatting alignment with the zmij crate.

Grep search confirms this codebase does not use any enum-as-map-key patterns. The serde usage here is standard JSON serialization of request/response bodies via serde_json::to_value(), which is unaffected.

Suggested next steps

1. Merge this PR - No changes required. This is a routine patch-level dependency update with no breaking changes for the usage patterns in this codebase.

General findings

None. The change is isolated to Cargo.lock with no code modifications needed.