update #1
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
release_to_pypi.yml
on: push
Publish release on PyPI
1m 15s
Annotations
1 error and 1 notice
Publish release on PyPI
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:blaylockbk/goes2go:environment:release`
* `repository`: `blaylockbk/goes2go`
* `repository_owner`: `blaylockbk`
* `repository_owner_id`: `6249613`
* `job_workflow_ref`: `blaylockbk/goes2go/.github/workflows/release_to_pypi.yml@refs/tags/2023.8.0`
* `ref`: `refs/tags/2023.8.0`
|
Publish release on PyPI
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
|