Consider Major Version Update For Breaking Changes

Hi,

I saw a similar thread here, but wanted to bring this issue up to stand on its own. My team and I spend quite a while debugging an obscure issue in our lower environments, to eventually track it down to the parameter order swap in propEq during the 0.28 to the 0.29 release.

Like the linked thread mentioned, our CI process (and I would wager most others out there) auto increment packages for patch and minor version changes. Please consider updating your versioning to match semvar practices to prevent issues like this in the future.

I've written a LOT of code at previous companies using propEq and I can only imagine the fires happening over there.