Thank you for reporting this. I have updated it on GitHub. Since it is a warning and not an error I will add the fix into the next plugin release rather than make a release just for this issue. I plan on doing the next release after WordPress 5.0 is released officially.