v2.7.1 — Discord suggests host and container names, and the bot channel keeps the release link
Latest
Both of these come from @NotRetarded using the bot rather than reading it (#57).
Discord now suggests host and container names
Nothing in Discord's interface tells you what a free-text option will accept. It shows the description, then an empty field. So working out that the machine Docksentry runs on is called local was a puzzle to be solved — reasonable with one host, guesswork with five.
Both fields suggest the real names as you type now, and the container list follows whichever host you already picked. Suggestions, not fixed choices: a name you type yourself still works, which matters while a container is mid-rename.
The information was never secret. /hosts has listed it all along — just not where the typing happens.
It's set in one place for all 26 options rather than per command, so the next command to grow a host can't be added without it.
The bot channel kept the release link
The webhook renders a container name as a clickable link to its release page. The bot posted the name as plain code.
Not a formatting quirk — the method accepted source_url and used it for nothing, and the same omission cost the "Updates available" list its Source ↗ line and its version badge.
Fixed by deleting the second rendering rather than patching it: the bot channel inherits the webhook's embeds now and overrides nothing but the transport. The two are the same message by construction, so a change to one is a change to both. Two hand-written renderings of a single notification was one too many to keep in step, which is exactly how this drifted.
And
- The weekly report never reached the bot channel — or SMTP, ntfy, Gotify, Matrix, or Apprise. It writes its own list of recipients instead of going through the notifier facade, so every channel added since has quietly been missing from it. Same shape as the startup message in 2.7.0. The bot channel is wired in here; the rest of that list is a wider repair and is not in this release.
- The 2.7.0 changelog listed
context://and the unreachable-host reason twice, in two different lengths, from being written in two passes.
Nothing to do on upgrade.
