Skip to content

[BUILD] Adjust workflow to be multi-arch (#195) #20

[BUILD] Adjust workflow to be multi-arch (#195)

[BUILD] Adjust workflow to be multi-arch (#195) #20

Triggered via push November 14, 2025 09:23
Status Failure
Total duration 6m 5s
Artifacts 1

release.yml

on: push
publish-to-pypi
1m 57s
publish-to-pypi
publish-docker-image-to-ghcr
6m 1s
publish-docker-image-to-ghcr
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L94
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/

Artifacts

Produced during runtime
Name Size Digest
adobe~ops-cli~X49EFL.dockerbuild
138 KB
sha256:561cb6f0f78bf49dc6ad1a6d667b8588181b54bb4b4bd057125e3d62f4612fa8