I wonder if this patch has slipped through the net due to a process error on my part.
No error on your side.
I submitted this corrected v4 version on March 13th. Perhaps I should have not submitted a v4 and that has screwed something up, or perhaps folks are just busy ;-).
The latter. It fell through the cracks, sorry about that!