This happened in the version 0.18.2. By "next update" did you mean the upcoming 0.18.3?
Yes.... the next update... as in, the one after the current one :P
