v5.3.2
Previously when checking the version field, we only required the version of modified detection be greater than the previous version. We now require it to be exactly previous_version+1. This cuts down on weird gaps in detection versions between releases where a detection's version has been bumped several times between releases.
What's Changed
Full Changelog: v5.3.1...v5.3.2