Skip to content

Bump bandit from 1.7.4 to 1.9.4 #253

Bump bandit from 1.7.4 to 1.9.4

Bump bandit from 1.7.4 to 1.9.4 #253

Triggered via pull request March 1, 2026 14:22
Status Failure
Total duration 2m 16s
Artifacts 1

pr_build.yml

on: pull_request
build-develop-open  /  build-image
41s
build-develop-open / build-image
trivy-scans  /  build-image
1m 45s
trivy-scans / build-image
build-develop-merge  /  build-push-image
build-develop-merge / build-push-image
build-main-merge  /  build-push-image
build-main-merge / build-push-image
build-main-open  /  build-push-image
build-main-open / build-push-image
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
trivy-scans / build-image
The process '/usr/bin/git' failed with exit code 128
trivy-scans / build-image
couldn't find remote ref refs/heads/main
trivy-scans / build-image
couldn't find remote ref refs/heads/main
trivy-scans / build-image
couldn't find remote ref refs/heads/main
trivy-scans / build-image
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
trivy-scans / build-image
The process '/usr/bin/git' failed with exit code 128
trivy-scans / build-image
couldn't find remote ref refs/heads/main
trivy-scans / build-image
couldn't find remote ref refs/heads/main
trivy-scans / build-image
couldn't find remote ref refs/heads/main
Legacy key/value format with whitespace separator should not be used: Dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
trivy-scans / build-image
Unable to clean or reset the repository. The repository will be recreated instead.

Artifacts

Produced during runtime
Name Size Digest
kbase~relation_engine~R4Q3D6.dockerbuild Expired
45.4 KB
sha256:1ca54af3936f859392822acdfafac7f1be5afb4477380dd83402a33bfbe73217