Add release workflow for PyPI/ghcr.io and automated license checking #1198
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.
We should start releasing packages to PyPI (primarily to push our deps metadata cleanly) and to a container registry (for easier builds). This PR adds a release workflow that would initiate that process -- this must be tested carefully via release candidates first.
It also adds a
liccheck
workflow that reports any dependencies we use that follow non-permissive licenses, such as GPL. I think most likely, we need to at least find the licenses for these dependencies, add an extra section to our license file with them, so that we can push a pre-built docker image that contains the full source of these deps.