Fix build project#482
Conversation
* Adding explicit references to use nuget packages without known vulnerabilities
Test Results 75 files ±0 75 suites ±0 4m 5s ⏱️ +47s Results for commit 3b54fe4. ± Comparison against base commit 3d4989f. This pull request removes 10 and adds 8 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
Coverage Report for CI Build 24711697934Coverage remained the same at 97.885%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
|
I do not see any build problem in the last MAIN build!? |
All dependency update PRs fail because of this. |
lg2de
left a comment
There was a problem hiding this comment.
I recommend more detailed comment.
We do not know when an how Nuke will be updated to fix these vulnerabilities. Later it may be more difficult to map one comment to two packages.
Co-authored-by: Lukas Grützmacher <[email protected]>
|
I vote for moving along to a fork: https://github.com/gruke-build/src It's a drop-in replacement |
|
I came along this repo when checking NUKE PRs and recognize a reference to a fork. But: this fork also has the same dependencies as NUKE so wouldn't make a difference for now. But in the long term this could be it... |



IMPORTANT
./build.sh --target spellcheckor.\build.ps1 --target spellcheckbefore pushing and check the good outcomeLegal checklist