We fixed this in 4.0 but it's actually a bug in 3.x that I think deserves a dot-release fix.
We fixed this in 4.0 but it's actually a bug in 3.x that I think deserves a dot-release fix.