-
Notifications
You must be signed in to change notification settings - Fork 417
New issue
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
[Bug] CI Pipeline Does Not Fail when Vulnerable Dependencies Found #493 #497
Conversation
As we have 3 vulnerabilities, how can we move forward with this PR? Some of them were fixed by .NET MAUI team |
Oh good one! Why don't we get dependabot alerts on this repo? That should also catch these, right? |
Added dependabot. I added the flag |
Question №2, should we check Transitive vulnerabilities? we cannot fix them. |
bc540a1
to
c3154ec
Compare
c3a8c15
to
2bd8aaf
Compare
2bd8aaf
to
7ec73eb
Compare
Thanks Vlad!
The 3 vulnerabilities are in the
We should! We can always add an updated version of the specific NuGet Package that has fixed the vulnerability, like you've done by adding a direct reference to
I vote to check the entire solution. It's good to ensure we avoid vulnerabilities in every csproj, even if it's a Sample App or a Unit Test. |
I agree with everything Brandon said! |
Co-authored-by: Brandon Minnick <[email protected]>
…com/CommunityToolkit/Maui into 493-fail-on-vulnerable-dependencies
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Thanks Vlad!
I had just a small bit of feedback around the new environment variable in the pipeline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Vlad!!
Description of Change
Fail pipeline if has any vulnerability
Linked Issues
PR Checklist
approved
(bug) orChampioned
(feature/proposal)main
at time of PRAdditional information