From c9b8f666cd106cafd7ae36460a9bde4b991feb02 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Mon, 27 Jul 2026 07:31:37 +0200 Subject: [PATCH] =?UTF-8?q?docs(release):=20winget=20needs=20its=20source?= =?UTF-8?q?=20added=20first=20=E2=80=94=20say=20so?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reported within an hour of the announcement: `winget install unom.PunktfunkHost` answers "no package found". That is correct behaviour, not a broken package — Punktfunk is served from its own REST source, and winget only searches sources it has been told about. The notes said "after adding Punktfunk's package source once" without ever giving the command, so there was no way to act on it. Both commands are now spelled out, the `winget source add` one flagged as needing an Administrator terminal (it does), and the failure mode is stated explicitly so someone who hits it recognises it rather than filing it as a bug. The lead-in is untouched, so the Discord embed for v0.20.0 stays accurate and this needs no re-announcement — the release body is re-synced from this file. --- docs/releases/v0.20.0.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/releases/v0.20.0.md b/docs/releases/v0.20.0.md index b57ac982..e0ede183 100644 --- a/docs/releases/v0.20.0.md +++ b/docs/releases/v0.20.0.md @@ -36,13 +36,22 @@ Every library entry can now carry **platform, description, developer, publisher, ## New: install and update the Windows host with winget -Windows had **no update path at all** — no self-update, no package manager — so keeping a host current meant noticing that a release had happened and re-running an installer by hand. Now, after adding Punktfunk's package source once: +Windows had **no update path at all** — no self-update, no package manager — so keeping a host current meant noticing that a release had happened and re-running an installer by hand. Now it is two commands. + +Punktfunk lives in **its own package source**, not the public winget catalogue, so add that first. Once per machine, from an **Administrator** terminal: + +``` +winget source add -n punktfunk https://winget.punktfunk.unom.io -t Microsoft.Rest +``` + +Then install, and from then on upgrade: ``` winget install unom.PunktfunkHost +winget upgrade unom.PunktfunkHost ``` -and `winget upgrade` from then on. The source is ours rather than the public catalogue, and it knows about every release, so you can pin an older version or upgrade from one. +**If you skip the first command, `winget install unom.PunktfunkHost` will tell you no package was found** — winget only searches the sources it knows about, and Punktfunk is not in the public one. The source knows about every release, so you can also pin an older version with `--version` or upgrade from one. A silent install shows you the same disclosures the wizard does — including where the bundled virtual audio device comes from — and takes the same defaults the wizard offers, so installing without a screen doesn't quietly get you a different machine.