I confirm the issue for both 1.0.0 and 1.0.3. It appears fixed in 1.0.4, so a bump to 1.0.4 (issue 1034523) would fix this issue as a side effect.

Reply via email to