Skip to content

Bump gunicorn from 20.1.0 to 25.1.0 #245

Bump gunicorn from 20.1.0 to 25.1.0

Bump gunicorn from 20.1.0 to 25.1.0 #245

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

pr_build.yml

on: pull_request
build-develop-open  /  build-image
46s
build-develop-open / build-image
trivy-scans  /  build-image
1m 38s
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~PQ728A.dockerbuild
45.5 KB
sha256:f8f29470403cd66ce3eb52bb0269a7c21f9deab3b8bd1522735ebc6cb6a802e2