You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently once version of the package in excluded packages is changed license validation step fails. This adds unneeded friction to ci/cd pipelines. While this might be the intention for some being able to provide an npm semver compliant version would benefit at least some of the users.
Describe the solution you'd like
Allow semver, so instead of always providing the exact version one can use some of the following:
Describe alternatives you've considered
AFAIK the only alternative would be to either change the version of the packages or exclude the license completely, that is not secure.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently once version of the package in excluded packages is changed license validation step fails. This adds unneeded friction to ci/cd pipelines. While this might be the intention for some being able to provide an npm semver compliant version would benefit at least some of the users.
Describe the solution you'd like
Allow semver, so instead of always providing the exact version one can use some of the following:
Describe alternatives you've considered
AFAIK the only alternative would be to either change the version of the packages or exclude the license completely, that is not secure.
The text was updated successfully, but these errors were encountered: