This usually happens when we already have a nuget package with the same version already hosted on nuget. AFAIK, since we are not allowed to "replace" a package on nuget, is it possible for you to fail instead? That way, if this is already part of a pipeline, the pipeline would actually fail and it would be a reminder for us to update the version.