Nice to hear that things are going forward. We have workaround in place for the issue, so no problem.
I noticed this when I last time tried to remove that workaround. I will take another look at that when we upgrade our dependency versions.