Upgrade log4net dependencies#175
Merged
Merged
Conversation
Update vulnerable log4net references to patched versions, including the legacy vendored DebugEngine assembly. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Upgrade vulnerable log4net references to patched versions so Dependabot no longer flags the XML external entity issue in older log4net releases.
The .NET Framework 4.7.2 PackageReference projects now use log4net 3.3.0. The legacy net45 DebugEngine path keeps using a compatible 2.x assembly, updated to log4net 2.0.17, and the matching root packages.config entry was updated as well.
Validation:
dotnet restore .\PowerShellToolsPro\PowerShellToolsPro.csproj --nologodotnet restore .\PowershellTools.Common\PowershellTools.Common.csproj --nologo