Fix plug-in peerDep check

zFernand0 commented 4 months ago

What It Does

Remove the warnings at plug-in install time that appear, even though the plug-in peerDep version-range satisfies the requirement.

How to Test

First you would want to reproduce the issue:

Globally install any of the CLI versions tagged as 7.0.0-next.###
- https://github.com/zowe/zowe-cli/tags?after=v7.0.0
Modify a plug-in's peerDep version of imperative to >=5.0.0-next.0 <5.0.0.
Install your plug-in
Notice that there is a warning at install time

Then you can test this branch:

Build this branch and install/link it globally
Update the plug-in peerDep version to >=8.0.0-next.0 <8.0.0
Install the plug-in
Notice that there is no warning at install time 😋

Review Checklist I certify that I have:

[x] tested my changes
[x] added/updated automated tests
[x] updated the changelog
[x] followed the contribution guidelines

Additional Comments

This follows the same behavior as https://semver.npmjs.com/

Feel free to go to the website and enter the values @zowe/imperative and >=5.0.0-next.0 <5.0.0 😋

Also, this GIF might make things easier to review: temp

codecov[bot] commented 4 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.93%. Comparing base (b840120) to head (2e1d2d0). Report is 1 commits behind head on next.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## next #2067 +/- ## ======================================= Coverage 90.93% 90.93% ======================================= Files 616 616 Lines 17359 17359 Branches 3671 3672 +1 ======================================= Hits 15786 15786 Misses 1572 1572 Partials 1 1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

zFernand0 commented 4 months ago

This PR can wait until after to following PR is merged into next to avoid any confusion/conflicts 😋