Skip to content
Auto Release

Auto Release #156

Sign in to view logs

Auto Release

Auto Release #156

Manually triggered January 2, 2026 18:48
@MarvinSchenkelMarvinSchenkel
⁠ 2367b3c
stable
Status Failure
Total duration 8m 15s
Artifacts 2

auto-release.yml

on: workflow_dispatch
check-and-release
20s
check-and-release
Trigger Release Workflow  /  Determine release branch
2s
Trigger Release Workflow / Determine release branch
Matrix: Trigger Release Workflow / Run tests and linting before release / test
Trigger Release Workflow  /  ...  /  lint
1m 8s
Trigger Release Workflow / Run tests and linting before release / lint
Trigger Release Workflow  /  Validate version and build Python artifact
48s
Trigger Release Workflow / Validate version and build Python artifact
Trigger Release Workflow  /  Create GitHub Release with Release Drafter
1m 27s
Trigger Release Workflow / Create GitHub Release with Release Drafter
Trigger Release Workflow  /  Build and push Music Assistant Server container to ghcr.io
2m 47s
Trigger Release Workflow / Build and push Music Assistant Server container to ghcr.io
Trigger Release Workflow  /  Publish release to PyPI (stable releases only)
17s
Trigger Release Workflow / Publish release to PyPI (stable releases only)
Trigger Release Workflow  /  Update Home Assistant Add-on Repository
12s
Trigger Release Workflow / Update Home Assistant Add-on Repository
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
Trigger Release Workflow / Publish release to PyPI (stable releases only)
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:music-assistant/server:ref:refs/heads/stable` * `repository`: `music-assistant/server` * `repository_owner`: `music-assistant` * `repository_owner_id`: `71128003` * `workflow_ref`: `music-assistant/server/.github/workflows/auto-release.yml@refs/heads/stable` * `job_workflow_ref`: `music-assistant/server/.github/workflows/release.yml@refs/heads/stable` * `ref`: `refs/heads/stable` * `environment`: `MISSING` See https://docs.pypi.org/trusted-publishers/troubleshooting/ for more help.
Trigger Release Workflow / Publish release to PyPI (stable releases only)
Potential workflow misconfiguration: The claims in this token suggest that the calling workflow is a reusable workflow. In particular, this action was initiated by: music-assistant/server/.github/workflows/release.yml@refs/heads/stable Whereas its parent workflow is: music-assistant/server/.github/workflows/auto-release.yml@refs/heads/stable Reusable workflows are **not currently supported** by PyPI's Trusted Publishing functionality, and are subject to breakage. Users are **strongly encouraged** to avoid using reusable workflows for Trusted Publishing until support becomes official. Please, do not report bugs if this breaks. For more information, see: * https://docs.pypi.org/trusted-publishers/troubleshooting/#reusable-workflows-on-github * https://github.com/pypa/gh-action-pypi-publish/issues/166 — subscribe to this issue to watch the progress and learn when reusable workflows become supported officially

Artifacts

Produced during runtime
Name Size Digest
music-assistant~server~KVQ62S.dockerbuild
185 KB
sha256:d2f85f3d195e51bcea6a60843da6c1a4b632a90388895d2370e1e211870ad7c8
release-dists
62.7 MB
sha256:ec92ca2f4f9ea029bcdff5dd1dc80eb0374d3781e9814d4d4f7c63f62dbacc8b