Thanks for the report! Confirmed bug from localization push, and this should be fixed in next release.