That's a small bug that's fixed in v1.5.0