use asyncio.new_event_loop in tests for compatibility with Python 3…
#21
release.yml
on: push
Build a pure Python wheel and source distribution
20s
Publish release
Publish in-dev package to test.pypi.org
11s
Annotations
1 error
|
Publish in-dev package to test.pypi.org
Trusted publishing exchange failure:
Token request failed: the server refused the request for the following reasons:
* `invalid-publisher`: valid token, but no corresponding publisher (Publisher with matching claims was not found)
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:brunns/PyHamcrest:environment:publish-test-release`
* `repository`: `brunns/PyHamcrest`
* `repository_owner`: `brunns`
* `repository_owner_id`: `227768`
* `workflow_ref`: `brunns/PyHamcrest/.github/workflows/release.yml@refs/heads/main`
* `job_workflow_ref`: `brunns/PyHamcrest/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`
* `environment`: `publish-test-release`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
Package Metadata
|
4.67 KB |
sha256:3ba02d99f9544e64b5c554c21a11b3d29f521502e35be86c0004c258b62be9ba
|
|
|
Packages
|
182 KB |
sha256:98d07820a42e9a045a7a010438eddce77450fbe95851f357d7a1a677c29691d5
|
|
|
PyPI README
|
3.84 KB |
sha256:ae53fc714d55d3efddce97943a018de2c67111859dbab7db40ef81aeb2df5e22
|
|