Thanks for the heads-up! The add-on should account for that normally (by using a fairly silly approach - writing a dummy file to update the mtime). But that must have broken with 1.4.0. Added to the issue tracker here and will look into it.
Cheers for the .55 change as well 