chore(deps): bump github.com/bluekeyes/go-gitdiff from 0.4.0 to 0.6.1

[dependabot]

Bumps github.com/bluekeyes/go-gitdiff from 0.4.0 to 0.6.1.

Release notes

Sourced from github.com/bluekeyes/go-gitdiff's releases.

v0.6.1

Fixes

• Fix out-of-bounds panic in timestamp parsing (#28)
• Fix panic when parsing certain invalid text fragments (#29)
• Return an error when parsing text fragments that contain only context lines (#29)
• Use ioutil to retain compatibility with Go versions prior to 1.16 (#31)

v0.6.0

API Breaks

• Improve the behavior of the LineReaderAt interface when the final line does not have a newline character. This change is only relevant for clients that define LineReaderAt implementations and should not affect most users of the library. If you use a custom LineReaderAt implementation, please review the documentation and update your implementation to avoid errors (#27).

Fixes

• Fix apply errors (unexpected EOF) with files that are multiples of 1024 bytes and have no final newline (#27).

v0.5.2

Improvements

• Decode quoted-printable UTF-8 subjects when parsing mail-formatted patch headers (#25)

v0.5.1

Improvements

• Relax requirements for mail-formatted patch headers (#20)

Fixes

• Fix parsing for file names with spaces (#24)

v0.5.0

Improvements

• Remove email decoration ([PATCH], re:, etc) from patch titles in ParsePatchHeader (#17). Any content removed in this way is stored in the SubjectPrefix field of PatchHeader.
• Remove email trailers (content after a --- line) from patch bodies in ParsePatchHeader (#19). Any content removed in this way is stored in the BodyAppendix field of PatchHeader.

Commits

• 52645c6 Use ioutil for compatibility with older Go versions (#31)
• f23f745 Add note about fuzz testing to README
• 4f54037 Return errors for empty text fragments (#29)
• b6a9011 Fix out-of-bounds panic parsing timestamps (#28)
• 53bcdf7 Fix EOF error for some files without final newline (#27)
• b575654 Decode quoted-printable UTF8 in email subjects (#25)
• 3772c9e Fix parsing for file names with spaces (#24)
• b666609 Remove deprecated actions commands (#22)
• 8cd57be Update development status in README
• b846b2c Relax email header requirements (#20)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[jenkins-x-bot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[garethjevans]

/ok-to-test

[garethjevans]

/lgtm

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: garethjevans

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [garethjevans]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jenkins-x-bot]

New changes are detected. LGTM label has been removed.