Skip to content
Auto Release

Auto Release #52

Sign in to view logs

Auto Release

Auto Release #52

Manually triggered November 14, 2025 14:07
@MarvinSchenkelMarvinSchenkel
⁠ 0408a19
stable
Status Failure
Total duration 5m 59s
Artifacts 2

auto-release.yml

on: workflow_dispatch
check-and-release
18s
check-and-release
Trigger Release Workflow  /  Run tests and linting before release
1m 52s
Trigger Release Workflow / Run tests and linting before release
Trigger Release Workflow  /  Validate version and build Python artifact
41s
Trigger Release Workflow / Validate version and build Python artifact
Trigger Release Workflow  /  Create GitHub Release with Release Drafter
30s
Trigger Release Workflow / Create GitHub Release with Release Drafter
Trigger Release Workflow  /  Build and push Music Assistant Server container to ghcr.io
2m 6s
Trigger Release Workflow / Build and push Music Assistant Server container to ghcr.io
Trigger Release Workflow  /  Publish release to PyPI (stable releases only)
13s
Trigger Release Workflow / Publish release to PyPI (stable releases only)
Trigger Release Workflow  /  Update Home Assistant Add-on Repository
7s
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~SSAPJU.dockerbuild
145 KB
sha256:6514263b9bb2986bc779562e3ce6d49f863ec65896a6a8e3aca5591d538b87d2
release-dists
43.5 MB
sha256:1d8bcc251607aff45cf29b44008d97ff6a2a81afca522e28630a3555aa2396f2