Yes, unfortunately this problem was fixed after the 3.0.3 was published.
Reviewed the test results with Jakub, situation looks like expected.
Yes, unfortunately this problem was fixed after the 3.0.3 was published.