Update debian files with workflows #18
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
* add Github CI workflow to build debs against multiple debian release * add hatchling to build deps, seems to be only available starting with debian bookworm * ubuntu PPA was happy with pyproject.toml and setuptools backend Signed-off-by: Steve Arnold <[email protected]>
* includes a bandit workflow to track security "issues" * also deconflict and dedup ci workflow (github workaround) Signed-off-by: Steve Arnold <[email protected]>
|
Unless I see a "Yes" comment on the bandit workflow I'll push another PR commit without it. |
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.
It turns out
hatchis not available prior to bookworm. I also added a bandit workflow that annotates PR checks to illustrate why the previous PR had the XML patch. The current report is here which you can see by clicking on Bandit commentsNote the insecure XML warning has an actual CVE associated with it.