Skip to content

Commit 9ed360b

Browse files
authored
Update README.md (latest is still building) (#135)
1 parent 3e98f79 commit 9ed360b

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@ A Docker image for [librespot](https://github.com/librespot-org/librespot)
44

55
## News
66

7-
The current `latest` image is built on the current `dev` branch of [librespot](https://github.com/librespot-org/librespot), at [this commit](https://github.com/librespot-org/librespot/commit/ba3d501b08345aadf207d09b3a0713853228ba64).
7+
The upcoming `latest` image, building now (see [here](https://github.com/GioF71/librespot-docker/actions/runs/16904408175)) on the current `dev` branch of [librespot](https://github.com/librespot-org/librespot), at [this commit](https://github.com/librespot-org/librespot/commit/ba3d501b08345aadf207d09b3a0713853228ba64).
8+
In the meantime (3h ETA) you can use the already available image tagged as `develop-2025-08-11-bookworm`, see [on DockerHub](https://hub.docker.com/r/giof71/librespot/tags?name=develop-2025-08-11).
89
This fixes [this issue](https://github.com/GioF71/librespot-docker/issues/128) even using the `latest` image, without the need to apply the suggested workaround (for that, thanks to [this post on Moode Audio forum](https://moodeaudio.org/forum/showthread.php?tid=7915&pid=65727#pid65727)).
910
I will use [my fork of librespot](https://github.com/GioF71/librespot-docker), purposedly created just to have a tag named `dev-2025-08-11` at the specified commit.
1011

0 commit comments

Comments
 (0)