@SilverEagle Adding a deprecation warning message to v3 and v4, along with a v5 release with the change is how I would have approached this. This change bit us yesterday and I was lucky to discover the cause quickly. Could have been hours of debugging. Semver exists for a reason.