Skip to content

Build on workflow yaml change #3

Build on workflow yaml change

Build on workflow yaml change #3

Triggered via push September 9, 2026 08:25
Status Success
Total duration 44s
Artifacts 1
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
release
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://docs.slack.dev/legacy/legacy-messaging/legacy-secondary-message-attachments for more details).
release
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: privoxy/Dockerfile#L36
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The MAINTAINER instruction is deprecated, use a label instead to define an image author: privoxy/Dockerfile#L6
MaintainerDeprecated: Maintainer instruction is deprecated in favor of using label More info: https://docs.docker.com/go/dockerfile/rule/maintainer-deprecated/

Artifacts

Produced during runtime
Name Size Digest
vimagick~dockerfiles~X0QVFF.dockerbuild
73.3 KB
sha256:14af742a3cf67e3546ad49cf8fb280047939c506943b358fad26762345a0a006