Automatic Release Creation #1
macratrelease.yml
on: schedule
create-metadata
6s
Matrix: publish-npm
Matrix: publish-pypi
create-release
0s
Annotations
12 errors
|
Build slack
Process completed with exit code 1.
|
|
Build everything
Process completed with exit code 1.
|
|
Build memory
Process completed with exit code 1.
|
|
Build aws-kb-retrieval-server
Process completed with exit code 1.
|
|
Build sqlite
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:macrat/mcp-servers:environment:release`
* `repository`: `macrat/mcp-servers`
* `repository_owner`: `macrat`
* `repository_owner_id`: `11837387`
* `workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `job_workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Build filesystem
Process completed with exit code 1.
|
|
Build fetch
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:macrat/mcp-servers:environment:release`
* `repository`: `macrat/mcp-servers`
* `repository_owner`: `macrat`
* `repository_owner_id`: `11837387`
* `workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `job_workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Build puppeteer
Process completed with exit code 1.
|
|
Build sentry
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:macrat/mcp-servers:environment:release`
* `repository`: `macrat/mcp-servers`
* `repository_owner`: `macrat`
* `repository_owner_id`: `11837387`
* `workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `job_workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Build github
Process completed with exit code 1.
|
|
Build git
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:macrat/mcp-servers:environment:release`
* `repository`: `macrat/mcp-servers`
* `repository_owner`: `macrat`
* `repository_owner_id`: `11837387`
* `workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `job_workflow_ref`: `macrat/mcp-servers/.github/workflows/release.yml@refs/heads/main`
* `ref`: `refs/heads/main`
See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
|
|
Build gdrive
Process completed with exit code 1.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
release-notes
|
316 Bytes |
|