Minor updates do not handle major version zero correctly

[lesleh]

• I have searched for similar issues

---

Steps to Reproduce

Steps:

Current Behavior

When passing -t minor, version updates with major version zero get included, even though major version 0 can include breaking changes and should be treated the same as semver major.

For example, if a package is on 0.1.0, and there's a new version called 0.2.0, it will update, even though it shouldn't.

Expected Behavior

Minor version increments when the major version is zero should be excluded from being updated.

[raineorshine]

Hi, thanks for reporting.

Major version zero semantics are specifically part of semver. We've opted to treat -t minor and -t patch as "strict" updates of just the respective version digit for simplicity. I recommend -t semver for smarter upgrades that follow semver rules.

As an aside, the primary purpose of npm-check-update is to break your dependencies in a controlled fashion. There's always npm update for the typical semver upgrades that avoid breaking changes. I added -t semver for convenience.