chore(deps): update rust crate json-escape to 0.2.0

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Type	Update	Change
json-escape	dev-dependencies	minor	0.1.1 -> 0.2.0

---

Release Notes

veecore/json-escape (json-escape)

v0.2.0

Compare Source

Fixed

• Prevented pointer provenance loss in iterators (unescape and escape). The internal state slice (self.bytes) now correctly points to an empty subslice of the original input buffer after completion. This prevents potential pointer arithmetic underflow and Undefined Behavior (UB).

Refactoring

• Major internal refactoring of the unescape implementation. The core logic has been moved from lib.rs into explicit.rs, and the public unescape functions now use the faster, dedicated explicit::Unescape iterator. This improves code organization and developer focus.

⚠️ Breaking Change (Behavioral)

• Error state truncation is now immediate when using .display_utf8_lossy() after encountering an invalid escape sequence (e.g., \z, incomplete Unicode).
  • Previously, the iterator could yield some leading, successfully unescaped data before the error stopped processing, allowing partial data to be displayed.
  • The new, optimized iterator structure stops processing immediately upon error discovery, resulting in no partial data being yielded or displayed.

v0.1.3

Compare Source

Fixed

• Corrected offset for Unicode escape errors. Previously, an incorrect manual adjustment of +2 was applied to the error offset, causing invalid escape sequences like \uD83D to report the wrong position. This change removes the redundant adjustment, ensuring error positions are now reported accurately.

v0.1.2

Compare Source

Added

• New explicit module providing an alternative, fine-grained streaming API for both escaping and unescaping.
  • The iterators in this module yield structured EscapedChunk and UnescapedChunk types, allowing users to inspect literal text and modified characters separately.
  • This new API offers improved performance in several unescaping scenarios (e.g., up to 2x faster pure iteration with dense/sparse escapes).

Changed

• Updated crate description in Cargo.toml and README to better highlight ergonomics, correctness, and RFC compliance alongside high performance.

Fixed

• Corrected a critical panic in the SIMD-accelerated escape logic that occurred when processing strings containing multi-byte Unicode characters on x86_64 targets.

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package json-escape@0.1.1 --precise 0.2.0
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

[codspeed-hq]

CodSpeed Performance Report

Merging #23 will not alter performance

_{Comparing renovate/json-escape-0.x (69546ca) with main (8ddb6ae)}

Summary

✅ 4 untouched
⏩ 6 skipped¹

Footnotes

1. 6 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩