Skip to content

chore: add missing permission to release workflow #3

chore: add missing permission to release workflow

chore: add missing permission to release workflow #3

Triggered via push July 15, 2025 21:40
Status Failure
Total duration 1m 26s
Artifacts 4

release.yml

on: push
Matrix: unittests / unittests
Fit to window
Zoom out
Zoom in

Annotations

1 error
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 (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:runemalm/codius-cli:ref:refs/heads/master` * `repository`: `runemalm/codius-cli` * `repository_owner`: `runemalm` * `repository_owner_id`: `1846207` * `workflow_ref`: `runemalm/codius-cli/.github/workflows/release.yml@refs/heads/master` * `job_workflow_ref`: `runemalm/codius-cli/.github/workflows/release.yml@refs/heads/master` * `ref`: `refs/heads/master` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.

Artifacts

Produced during runtime
Name Size Digest
junit-report-3.10 Expired
677 Bytes
sha256:02aba576b58e9952ecff1e902368d3a9e79fc1235c6327df07d98f56d5384743
junit-report-3.11 Expired
677 Bytes
sha256:7bf28d75120de7510769760cb726da831f059deefc19cfb649484b0e53d0100c
junit-report-3.12 Expired
676 Bytes
sha256:7b6b385dd93d223b11a8cd13cb8d2a0390611ebbfa495b7208d0ea87157c9e46
junit-report-3.9 Expired
676 Bytes
sha256:888965e824a6e6caf6ed46bc0a63f12f648e20b6322292da56bdedddd7b3307b