Skip to content

chore(deps): update rust #795

chore(deps): update rust

chore(deps): update rust #795

Triggered via pull request June 30, 2026 13:02
Status Success
Total duration 8m 26s
Artifacts 1

build-image.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
build
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, aws-actions/configure-aws-credentials@b47578312673ae6fa5b5096b330d9fbac3d116df, docker/build-push-action@14487ce63c7a62a4a324b0bfb37086795e31c6c1, docker/login-action@74a5d142397b4f367a81961eba4e8cd7edddf772, docker/metadata-action@902fa8ec7d6ecbf8d84d538b9b233a880e428804, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L2
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L11
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L6
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes: Dockerfile#L20
WorkdirRelativePath: Relative workdir "app" can have unexpected results if the base image changes More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/
Relative workdir without an absolute workdir declared within the build can have unexpected results if the base image changes: Dockerfile#L4
WorkdirRelativePath: Relative workdir "build" can have unexpected results if the base image changes More info: https://docs.docker.com/go/dockerfile/rule/workdir-relative-path/

Artifacts

Produced during runtime
Name Size Digest
arkedge~hubhook~LUI1QW.dockerbuild
122 KB
sha256:12cfd6f775b32a5716ad35cf11d8904870ac743722d1fa1a889d15c117681fc1