Skip to content

Release to PyPI and as OCI image #2

Release to PyPI and as OCI image

Release to PyPI and as OCI image #2

Re-run triggered November 16, 2023 14:33
Status Failure
Total duration 56s
Artifacts

release.yaml

on: release
pypi-publish
39s
pypi-publish
publish-image
0s
publish-image
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
pypi-publish
Trusted publishing exchange failure: Token request failed: the server refused the request for the following reasons: * `invalid-publisher`: valid token, but no corresponding publisher (All lookup strategies exhausted) This generally indicates a trusted publisher configuration error, but could also indicate an internal error on GitHub or PyPI's part. The claims rendered below are **for debugging purposes only**. You should **not** use them to configure a trusted publisher unless they already match your expectations. If a claim is not present in the claim set, then it is rendered as `MISSING`. * `sub`: `repo:collective/collective.elastic.ingest:environment:release` * `repository`: `collective/collective.elastic.ingest` * `repository_owner`: `collective` * `repository_owner_id`: `362867` * `job_workflow_ref`: `collective/collective.elastic.ingest/.github/workflows/release.yaml@refs/tags/2.0.0b1` * `ref`: `refs/tags/2.0.0b1`
pypi-publish
Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field