Seems this problem was introduced with 0.2.8. 