Skip to content

feat: enhance logging with Rich console output and remove log format #20

feat: enhance logging with Rich console output and remove log format

feat: enhance logging with Rich console output and remove log format #20

Triggered via push March 27, 2026 04:56
Status Success
Total duration 4m 16s
Artifacts 2

ci-cd.yaml

on: push
cache  /  build-cache
6s
cache / build-cache
lint  /  ruff-lint
7s
lint / ruff-lint
test  /  unit-test-coverage
13s
test / unit-test-coverage
docker-build-and-image-scan  /  build-and-scan
53s
docker-build-and-image-scan / build-and-scan
release  /  Semantic-Release
1m 36s
release / Semantic-Release
release  /  ...  /  build-and-scan
1m 3s
release / Docker-Release / build-and-scan
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
cache / build-cache
Cache save failed.
lint / ruff-lint
Cache save failed.
test / unit-test-coverage
Cache save failed.
docker-build-and-image-scan / build-and-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
release / Docker-Release / build-and-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
milsman2~python-response-time~M15NO5.dockerbuild Expired
50.5 KB
sha256:69fc45ec951a1c6ccbc276fdd2542b9574d68e19af53d36916cb33a390d8c791
milsman2~python-response-time~N53DL1.dockerbuild Expired
51.4 KB
sha256:718c8ed1fae8ec7bc968cc96e1689751f0ba463b2c99e684adf62c4b57d67839