We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It doesn't make much sense to list patch versions in the dependency check. We should filter these out.
It might also be worth considering doing this with minor versions as well.
Here is an actual example of an patch version change:
1. Information: There are updates for 1 dependencie(s): esbuild ^0.20.0 → ^0.20.1
Note. Semantic versioning should normally be structured like this: MAJOR.MINOR.PATCH
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It doesn't make much sense to list patch versions in the dependency check. We should filter these out.
It might also be worth considering doing this with minor versions as well.
Here is an actual example of an patch version change:
Note. Semantic versioning should normally be structured like this: MAJOR.MINOR.PATCH
The text was updated successfully, but these errors were encountered: