Bump diff to 4.* to resolve github warning

[StoneCypher]

I use documentation, which uses disparity, which uses diff from four years ago (1.3.2 vs 4.0.1 current)

An obscure bug is marked high severity (wrongly) on Github's warning system. Bumping diff fixes it with no code changes. Tests continue to pass.

Fixes #3

Caused by this

Thanks kindly

[StoneCypher]

Also referenced as documentationjs/documentation#1257

[StoneCypher]

well that sucks, i don't get to be a contributor after all because someone else did it again six months later :(

[ruyadorno]

hi @StoneCypher I'm really really sorry you had to go through this 😞 it was totally not my intention - to make it clear the project seemed abandoned and I just asked Miller for access in order to at least fix the security issue #3 so that's why I rushed all fixes and pushed instead of merging community contributions. Looking back now that was definitely wrong.

I really believe in open source and the power of the community so I'm really sad to let down someone that put effort into participating like you did. I understand in case you can't forgive me but what I did in an effort to make up for this big mistake was to merge your commit into master in its current state, so that you'll get to be a contributor.

Many thanks for your contribution ❤️ and sorry again about all this.

[StoneCypher]

i appreciate your helping me get my badge, friend :)