Hide major updates in nested dependencies for "outdated" command
Description
If there is a major update, but it’s in a nested dependency that is controlled by one of your top level dependencies, don’t show it as being outdated since there’s nothing you can do anyway.
Activity
Show:
Brad WoodMarch 29, 2022 at 9:37 PM
The specific use case for this was the commandbox-migrations module (latest version) was pinned to the cfmigrations module version ^2.0 and there was a major 3.x release of the cfmgirations module so it was showing up as a “latest” update in the outdated command, but it was a false flag because there was literally no way a user could update the cfmigrations module past 2.x since, as a nested dependency, it’s version is controlled by the commandbox-migrations module.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
If there is a major update, but it’s in a nested dependency that is controlled by one of your top level dependencies, don’t show it as being outdated since there’s nothing you can do anyway.