Yes, that fixed to issue.. at least when developers have pulled latest changed from

v8/contrib

or

v9/contrib

branches, but it developers haven't yet and commit to existing PRs they will probably still get the error mail.. 🙂