[Marketen]

Since 2026-10-28 ~19:50 UTC the Tor network consensus lists Desc=3 Microdesc=3 as required protocols. Tor < 0.4.9 now refuses to work as a client:

[err] At least one protocol listed as required in the consensus is not supported by this version of Tor. [...] The missing protocols are: Desc=3 Microdesc=3

tor-hidden-service is built from alpine:edge with an unpinned tor, so each package release ships whatever Tor edge had at build time. The last release is from 2024, so users' hidden services shut down when the consensus changed and the monitors can no longer reach them: on the monitor side sum(up) dropped from ~279/307 targets to ~5–13, with No more HSDir available to query for the missing onions.

Change

• tor-hidden-service/Dockerfile: alpine:edge → alpine:3.23 and require tor>=0.4.9. The release build gets the latest Tor in Alpine 3.23 (currently 0.4.9.14); the build fails rather than ship Tor < 0.4.9.

The image is built once in CI at release time, so every user installing a given release gets the same Tor. Hidden service keys live in the tor-hidden-service volume and the tor user keeps uid 100, so onion addresses (and registrations) are preserved.

Tested locally: Tor 0.4.9.14 bootstraps to 100%; starting it on a volume with an existing hidden service keeps the same .onion hostname.

Merging to main publishes a new patch release via the Main workflow; users then need to update the package. Worth releasing a patch every few months so users keep getting a current Tor.

🤖 Generated with Claude Code