I assume this has been fixed in v2.1.0 or newer, like the "Fix committed" state indicates, so closing as "Fix released" now. In case there still something left to do here, feel free to re-open it.
I assume this has been fixed in v2.1.0 or newer, like the "Fix committed" state indicates, so closing as "Fix released" now. In case there still something left to do here, feel free to re-open it.