This issue will be resolved automatically once a stable version with a correct semantic versioning gets published.