Release new version #4
release.yml
on: push
build
30s
gh-release
6s
pypi-publish
20s
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:attakei/rst-package-refs:environment:pypi`
* `repository`: `attakei/rst-package-refs`
* `repository_owner`: `attakei`
* `repository_owner_id`: `668834`
* `job_workflow_ref`: `attakei/rst-package-refs/.github/workflows/release.yml@refs/tags/v0.1.0`
* `ref`: `refs/tags/v0.1.0`
|
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
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
packages-v0.1.0
Expired
|
21.2 KB |
|