Skip to content

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

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

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

Triggered via push October 22, 2024 17:34
Status Success
Total duration 15m 40s
Artifacts
Build Container Image
3m 2s
Build Container Image
Trigger deploy to dev
4m 39s
Trigger deploy to dev
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 dev
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 dev
Failed to find in_progress Jobs for Workflow Run 11465641647