Skip to content

fix: use priority image loading for heroes (#591) #308

fix: use priority image loading for heroes (#591)

fix: use priority image loading for heroes (#591) #308

Triggered via push October 24, 2024 20:26
Status Success
Total duration 8m 36s
Artifacts
Build Container Image
3m 6s
Build Container Image
Trigger deploy to prod
5m 9s
Trigger deploy to prod
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build Container Image
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/metadata-action@v4, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/build-push-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build Container Image
Unexpected input(s) 'build-args', valid inputs are ['context', 'images', 'tags', 'flavor', 'labels', 'sep-tags', 'sep-labels', 'bake-target', 'github-token']
Trigger deploy to prod
The following actions use a deprecated Node.js version and will be forced to run on node20: lasith-kg/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Trigger deploy to prod
Failed to find in_progress Jobs for Workflow Run 11506985805