accept 1.0 version number for set-release task

The `set-release` task didn't work with 1.0 version numbers. This PR fixes the misbehavior.
The check is there to avoid an error message calling `safeReplace`. `safeReplace` is doing it wrong! It bails, if the previous content and the updated content are the same. The check was added to detect if the replace operation has taken place. I think it makes more sense to check if the Regex matches, and only issue a warning if it doesn't.