Skip to content

[Dispatch] Release

[Dispatch] Release #1

Manually triggered November 22, 2024 05:41
Status Failure
Total duration 1m 46s
Artifacts

dispatch_release.yaml

on: workflow_dispatch
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
docker
buildx failed with: ERROR: failed to solve: failed to push ***/inventory-v2:0.0.dev1: unexpected status from POST request to https://public.ecr.aws/v2/megazone/spaceone/inventory-v2/blobs/uploads/: 404 Not Found
tagging
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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.
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
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):
pypi
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
docker
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/setup-qemu-action@v2, docker/setup-buildx-action@v2, docker/login-action@v2, docker/build-push-action@v4, aws-actions/configure-aws-credentials@v2, 8398a7/[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/