The bundled internal/channels/telegram package (17 files) is deleted; the
channel now ships as archipelago/channels/telegram, launched by archiemessaging
through the existing channel-extension machinery. An existing [chat.telegram]
config enables it with the same keys: the token stays a secret reference
(token_ref) the host resolves, allowed_user_ids and show_tool_calls map onto
extension settings. Per-org bots compose the same extension per org from the
org's credential binding. Reload support is now derived from a channels.Reloader
interface instead of a *telegram.Gateway assertion. The five host-only seams
(/update, release announcements, running versions, in-place show_tool_calls,
reload) are dropped from the channel and need a contract home or deletion.
AcceptInvitations accepted every pending repository invitation, so any
GitHub user could add the forge's account to a repository by sending an
invitation. The host now passes the connection's configured repositories
in AcceptInvitationsRequest and the extension leaves an invitation to
anything else pending. The Gitea forge is unchanged: it has no
invitations to accept.
The switch to the age library read only native age keys, so an
AGE_IDENTITY holding an SSH private key or a plugin identity (a YubiKey)
stopped working. Both parse again; a plugin that asks for input fails with
a message saying so, and a passphrase-protected identity file is refused
by name.
The age, Vault and SOPS engines shelled out with stderr discarded, so a
missing key and a broken setup both surfaced as 'exit status 1' and were
reported as the engine being unavailable. age now decrypts with the age
library and Vault reads over its API (KV v1 or v2, detected as the CLI
does), so neither needs a CLI on the host. SOPS still uses the CLI, whose
library would pull in every cloud KMS SDK, but decrypts the whole file to
JSON and looks the key up itself, so the key never reaches the CLI.
The engine listed secrets once per process. A failed first read made every
key unavailable until a restart, and a rotated or added secret never showed.
The list is now cached for five minutes, re-read sooner for a missing key,
never cached on failure, and a stale value is served while a refresh fails.
A gateway or SMTP failure skipped the message for the life of the process,
so mail sent during an outage was never answered. Only mail the channel
rejects is skipped now; the rest is retried on the next poll, and the
Message-ID as the source id makes the gateway replay a reply it already
produced instead of running the turn twice. Out-of-office replies, bulk and
list mail are ignored and replies are marked Auto-Submitted, so the channel
cannot loop with an auto-responder. Replies carry References for threading,
and port 465 uses implicit TLS.
Every call shared one SDK client whose context was background, so no caller
could cancel a Gitea request; each call now binds its own. LinkBranch
hand-built JSON over raw HTTP and posted to an endpoint Gitea does not have;
it sets the issue's ref through the SDK. PRState and VerifyPush matched error
text instead of the status, label lookup stopped at the first 100 labels,
merges ignored the repository's merge style, and a review of the token's own
pull request requested changes Gitea refuses.
Errors say what GitHub refused in its own words instead of the request URL
and an empty field list. Webhook review states arrive lower-case and were
never normalised, so a webhook-delivered change request did not read as one.
A review the token would post as REQUEST_CHANGES on its own pull request
comments instead, which GitHub accepts. Secondary rate limits wait up to two
minutes and retry.
The channel ran a hand-written SMTP listener and trusted the From address,
so anyone reaching the port could act as any user. It now uses go-imap,
go-message, go-msgauth and go-smtp; settings change accordingly.