Apparently not a bug but changed behaviour. Even documentation wise I'd say that everything should be clear at least with the latest available upstream version.