Skip to content

✨ 添加打包文件 #1

✨ 添加打包文件

✨ 添加打包文件 #1

Triggered via push September 8, 2023 15:24
Status Failure
Total duration 57s
Artifacts

release.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 notice
release
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:Enraged-Dun-Cookie-Development-Team/Avatar-Embed:ref:refs/tags/v0.1.0` * `repository`: `Enraged-Dun-Cookie-Development-Team/Avatar-Embed` * `repository_owner`: `Enraged-Dun-Cookie-Development-Team` * `repository_owner_id`: `82669195` * `job_workflow_ref`: `Enraged-Dun-Cookie-Development-Team/Avatar-Embed/.github/workflows/release.yml@refs/tags/v0.1.0` * `ref`: `refs/tags/v0.1.0`
release
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