Incorrectly updates "> 0.0.0" to "> 0.0.5" when 0.0.5 is latest

[henrik]

• I have searched for similar issues
• I am using the latest version of npm-check-updates
• I am using node >= 10.17

---

Steps to Reproduce

My package.json includes in its devDependencies:

"@barsoom/prettier-config": "> 0.0.0",

Current Behavior

Running npx npm-check-updates --upgrade --peer changes this constraint to > 0.0.5.

But since the latest version of the package is 0.0.5, there is no greater version, so npm install fails.

Same issue if the old version is > 0.0.1.

Expected Behavior

Either leaving the constraint as-is, or changing it to >= 0.0.5, or 0.0.5, or ^0.0.5, or similar.

Workaround

Changing > 0.0.0 to >= 0.0.0 fixes it. It becomes >= 0.0.5.

[raineorshine]

Definitely a bug! I'll get a fix into the next major version.

[raineorshine]

Fixed and published in v12.0.0.