Update dependencies to fix vulnerable usages #212
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.
Update vulnerable dependencies
Description
This pull request includes updates to various dependencies across multiple projects within the AasxServer solution. The changes aim to improve security, compatibility, and functionality by upgrading to the latest versions of key libraries.
Motivation and Context
These updates are essential to ensure that the projects are using the latest and most secure versions of their dependencies. Upgrading these libraries addresses known vulnerabilities, enhances performance, and improves overall compatibility.
How Has This Been Tested?
These changes have been tested by running the updated projects locally and ensuring that all functionality works as expected. Unit tests have been executed to verify that no existing functionality is broken by these updates. Additional manual testing has been performed to ensure that the new dependency versions do not introduce any regressions or issues.