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.
This removes most manual steps for creating a PyPI-release, and means that anyone with write access to this repo can create a pypi-release. The reason this works is because I (as PypI owner/maintainer) has added the workflow as a trusted workflow. For now I have also added my own workflow and have performed tests using it.
Also updating dependencies due to broken dependency between protobuf and grpio-tools
Markdown error is due to error in submodule
See https://github.com/eclipse-kuksa/kuksa-python-sdk/wiki/Release-Process for some notes on how this will affect release process