build(deps): bump diffy from 0.4.2 to 0.5.1 in /codex-rs

[dependabot]

Bumps diffy from 0.4.2 to 0.5.1.

Changelog

Sourced from diffy's changelog.

[0.5.1] - 2026-07-18

Fixed

• #85 Merge conflict markers are now always placed on their own lines. Previously, a conflicting hunk at the end of a file without a trailing newline glued the next marker onto its last content line, producing unparseable output. This matches git merge-file --diff3 behavior.

[0.5.0]- 2026-04-27

This is a major release introducing multi-file patch support, git binary diff handling, and no_std compatibility.

Breaking Changes

• #73 The crate is now no_std by default. Patch::to_bytes() and PatchFormatter::write_patch_into() now require the std feature. Add features = ["std"] to restore them.
• #46 Color support is now behind the color feature flag. Previously color was always available. Now PatchFormatter::with_color() requires enabling the color feature. The underlying implementation switched from nu-ansi-term to anstyle.

Added

• #55 #59 #61 #66 #74 #76 Multi-file patch support. Parse and apply unified diff and git diff output containing multiple files, including create, delete, modify, rename, and copy operations. Git binary patches (literal and delta) are supported behind the binary feature flag.
• #80 New apply example demonstrating multi-file patch application.

Fixed

• #51 #82 Patch::from_str / from_bytes no longer error on trailing non-patch content after a complete hunk, matching GNU patch and git apply behavior.

... (truncated)

Commits

• 51e8723 release 0.5.1
• 31de940 merge: keep conflict markers on their own lines (#85)
• 721fcb8 clippy: allow(question_mark)
• 6fa93d4 tests: update expected output for git v2.54
• 4197dca release 0.5.0
• e16c388 meta: exclude tests directory from package
• ea1d695 binary: mark BinaryPatchParseError::span pub(crate)
• 8591d7b docs: add changelog entry for v0.5.0
• 16d2380 chore: bump to 0.5.0
• 077a7c4 fix(patch): hunk range overflow panic
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)