Skip to content

Release: chore(release): 0.7.0 (#104) Signed-off-by: client-software-ci <[email protected]> #9

Release: chore(release): 0.7.0 (#104) Signed-off-by: client-software-ci <[email protected]>

Release: chore(release): 0.7.0 (#104) Signed-off-by: client-software-ci <[email protected]> #9

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via push April 1, 2024 17:16
Status Failure
Total duration 4m 39s
Billable time 7m
Artifacts
VerifyCommit
5s
VerifyCommit
PublishToRepository
50s
PublishToRepository
PublishToInternal
2m 50s
PublishToInternal
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
jusiskin
approved Apr 1, 2024
release and release
jusiskin
approved Apr 1, 2024
release

Annotations

1 error
PublishToRepository
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:OpenJobDescription/openjd-adaptor-runtime-for-python:environment:release` * `repository`: `OpenJobDescription/openjd-adaptor-runtime-for-python` * `repository_owner`: `OpenJobDescription` * `repository_owner_id`: `142452466` * `job_workflow_ref`: `OpenJobDescription/openjd-adaptor-runtime-for-python/.github/workflows/release_publish.yml@refs/heads/mainline` * `ref`: `refs/heads/mainline` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.