This fix has been in 2.4 branch since 2.4-beta1, so I am pretty sure that we have released it in 2.4.0.
This fix has been in 2.4 branch since 2.4-beta1, so I am pretty sure that we have released it in 2.4.0.