Updating dependencies to fix vulnerabilities#151
Merged
Conversation
erikbosch
requested review from
BjoernAtBosch,
MP91,
dennismeister93 and
doosuu
Contributor
Author
|
@BjoernAtBosch - this was the starting point for the wiki definition - that I realized that we somewhere should document when to update these two version labels. (As of today I think we can update them before we make a release as we do not test them in CI, but that might be more cumbersome if we actually starts testing them in CI as the new version do not yet exist in pypi when CI is run. I guess the examples better fit in another repo, especially as some of them like https://github.com/eclipse-velocitas/vehicle-app-python-sdk/tree/main/examples/seat-adjuster explicitly says that they cnanot be used from the sdk) |
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
2 participants
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.
There are some hypothetical vulnerabilities in v0.14.1 of this repo, so the examples and skeleton should preferably not use that one. I have just updated it to last release version (examples are anyway partially broken, see #141 )
We should better discuss how to handle these references when we do releases. Should we always update them before/after we create a new pypi release? Or should we in these two cases just remove version so we use "latest and greatest" velocitas-sdk