The additional 0 was most likely caused by a bug accidentally introduced in 1.2.0, until it was reported couple of weeks ago.
so, we reverted that behavior to stay backward-compatible in version 1.11.0.
3 Likes