According to the readme, it's 3.5.3
There is an inequality check, but then later there is something similar to a floating point epsilon check, looking for a minimum change. I'd post the source code where the issue is, but I don't want to post your source without permission.
Basically what I'm seeing in the source code is an inequality check against the current value, and if they're inequal, it basically checks if this.value (note that this does some rounding for the steps, which I'm assuming is why this optimization exists..) has changed by more than 0.001f. If it hasn't, it doesn't update.