feat: initial monorepo & server sdk (#61) #26
build-api.yml
on: push
Build API wheel/sdist
27s
Publish API release
25s
Annotations
1 error, 1 warning, and 1 notice
Publish API 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:livekit/python-sdks:ref:refs/tags/api-v0.1.0`
* `repository`: `livekit/python-sdks`
* `repository_owner`: `livekit`
* `repository_owner_id`: `69438833`
* `job_workflow_ref`: `livekit/python-sdks/.github/workflows/build-api.yml@refs/tags/api-v0.1.0`
* `ref`: `refs/tags/api-v0.1.0`
|
Build API wheel/sdist
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
Publish API 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
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
api-release
Expired
|
35.4 KB |
|