build(deps): bump similar from 2.7.0 to 3.2.0

[dependabot]

Bumps similar from 2.7.0 to 3.2.0.

Changelog

Sourced from similar's changelog.

3.2.0

• Added structured, line-oriented three-way merging through TextMerge, with merge and diff3 conflict output, configurable labels and marker sizes, owned and borrowed inputs, byte output, and whitespace-insensitive comparison.
• Added WhitespaceMode and TextDiffConfig::whitespace_mode for Git-style line comparisons that ignore changes in whitespace (-b) or all whitespace (-w).
• Changed Algorithm::Myers to reduce unmatched/confusing records and use Git-style bounded, non-minimal splits on expensive searches, and added Algorithm::RawMyers for the previous shortest-edit-script behavior without output-changing heuristics.
• Improved heuristics and performance for most algorithms other than LCS.
• Improved large-input performance by avoiding quadratic Histogram scans.

3.1.2

• Fixed Algorithm::Lcs deadline fallback emitting edits twice, which produced out-of-bounds DiffOp ranges and panics when consuming timed-out diffs. #97
• Fixed Algorithm::Lcs reporting identical subranges with zero-based indices instead of preserving the supplied range offsets. #98
• Fixed Algorithm::Lcs and Algorithm::Hunt emitting zero-length delete operations when both inputs are empty. #99

3.1.1

• Fixed DiffOp cursor positions when compacting adjacent inserts/deletes and in Algorithm::Histogram full-replacement output, ensuring operations form contiguous ranges. #95
• Renamed sample diff input files to a lexicographic caseNN.01.before_* / caseNN.02.after_* scheme.

3.1.0

• Added capture_diff_slices_by_key and capture_diff_slices_by_key_deadline as convenience helpers for diffing slices by derived keys.
• Fixed Compact emitting inconsistent DiffOp cursor positions after compaction, which could leave Delete/Insert operations with stale new_index/old_index values.
• Added explicit lifetime capture (+ use<...>) on iterator-returning APIs to improve compatibility with Rust 2024 lifetime capture behavior. #93

3.0.0

• Added a Git-style Histogram diff implementation exposed as Algorithm::Histogram, including deadline-aware Myers fallback and comprehensive regression/behavior tests.
• Raised MSRV to Rust 1.85 and moved the crate to Rust 2024 edition.
• Added a Hunt-style diff implementation exposed as Algorithm::Hunt.
• Added configurable inline refinement via InlineChangeOptions and

... (truncated)

Commits

• e380405 chore(release): prepare 3.2.0
• 9133b3d ref: Update changelog
• a56a53f feat(merge): add three-way text merging
• 7130d06 docs(examples): demonstrate whitespace-insensitive diffs
• a635843 feat(text): add whitespace-insensitive line diffs
• 6301178 perf(myers): preserve sparse matches with record reduction
• f16b309 perf(myers): add bounded heuristic search
• accea7d chore(clippy): resolve lint warnings
• 3a5162b perf(algorithms): fast-path nearly disjoint ranges
• fc32411 feat(fuzzing): add isolated performance campaign runner
• Additional commits viewable in compare view

[greptile-apps]

Greptile Summary

Updates the workspace-wide similar dependency from 2.7.0 to 3.2.0 and refreshes its lockfile entry, including the new transitive bstr dependency. Targeted checks confirm the apply-patch, engine diff, and no-audio TUI consumers continue to work with the updated version.

Confidence Score: 5/5

Safe to merge: the dependency update passed targeted checks for every direct workspace consumer.

No defects were found in the changed dependency resolution or its direct application paths.

Files Needing Attention: None.

T-Rex Logs

What T-Rex did

• I verified that the parent revision resolved similar = "2" and similar 2.7.0, and I inspected the upgraded lockfile to confirm it targets similar 3.2.0.
• I exercised the apply-patch test suite, targeted engine diff tests, and performed a no-audio TUI build check; all tests completed successfully.
• I confirmed that no production source was modified during verification and noted that pre-existing Cargo manifest warnings did not affect completion.
• Before capture I confirmed the parent revision resolved similar = "2" / similar 2.7.0, and after capture I recorded the exact targeted validation against similar 3.2.0 and its successful exit status.
• I verified that only the validation script was authored, no production code changes were made, and pre-existing Cargo manifest warnings were emitted but did not affect command success.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "build(deps): bump similar from 2.7.0 to ..." | Re-trigger Greptile}