Project's updates #5
Open
Conversation
This file contains 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
… at least in the near future and ensure the projects are more up to date using supported framework. EnableUnsafeBinaryFormatterSerialization = true to the projects using BinaryFormatter with is long deprecated and will be removed in net9 but for the time being this is a quick solution. Added TODO to upgrade Kaos.Combinatorics with a version where security vulnerabilities are resolved. Referenced .NET Framework 4.6.1 is upgraded to .NET Framework 4.8. Multiple dependencies are upgraded in TestCore.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The main reason for the changes was to address the reported vulnerability and update the projects to supported frameworks. Even though they are not necessary for the project generating the main nuget I decided to create a PR in case you'd like to do similar updates as well. The most important thing, I'd like to ask you to update the nuget package on nuget.org as long as to avoid vulnerability warnings we are forced to use locally built nuget where this issue is already resolved but the package is not yet updated on the server.