Prevent Security Vulnerability Errors from Magick by Not Treating Warnings as Errors#397
Merged
pete-tempo merged 1 commit intomainfrom Mar 1, 2026
Merged
Prevent Security Vulnerability Errors from Magick by Not Treating Warnings as Errors#397pete-tempo merged 1 commit intomainfrom
pete-tempo merged 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every time the NuGet vulnerability database flags a Magick version's security vulnerability, the dotnet build in InstallEngineMods or TempoROSCopyHandler treats it as an error and the build fails. This is because
<NuGetAudit>is enabled and Unreal's projects have<TreatWarningsAsErrors>that promotesNU1900-seriesaudit warnings to errors. This adds a Directory.Build.props file to the AutomationTool directory for 5.6 and 5.7 that sets<NuGetAudit>false</NuGetAudit>.