Skip to content

Releases

v1.2.4

Choose a tag to compare

@github-actions github-actions released this 17 Nov 13:36

The GitHub organization FreshLabDev is now asterfield-dev, and the bot moves
with it. Nothing a person sees in Telegram changes.

Changed

  • Images are published as ghcr.io/asterfield-dev/branchy. The
    organization was renamed, and GitHub Container Registry does not redirect
    the old name: ghcr.io/freshlabdev/branchy answers 403. Point the
    deployment's image at the new path; every earlier digest is there under it
    too.
  • tg moves from v0.1.0 to v0.4.0-alpha.2, whose module path is
    github.com/asterfield-dev/tg. A press on a button under an inline message
    now arrives without a message; branchy sends none, so such a press is
    answered and ignored.
  • Links, the module path and the docs point at github.com/asterfield-dev.
    Old links still redirect.

Known Limitations

  • Released as a stable patch without a pre-release first, at the owner's
    request: the change is the organization rename and the tg upgrade, checked
    by the full test suite, not by a run on a test bot.

Container image

ghcr.io/asterfield-dev/branchy@sha256:ec6510400719a4acd0f8f59b5be03ebd46659a0240721e0ebf7363dcba40a91d

v1.2.3

Choose a tag to compare

@amtiYo amtiYo released this 14 Nov 19:42

Branchy on by.ws04.cc, on the stable Telegram client, with every known Go
advisory against it closed. This is v1.2.3-alpha.2, which has run the
production bot since 20 October, plus the security updates below. Coming from
v1.2.2, read the two alphas under this section: the address change in
v1.2.3-alpha.1 is the one an operator has to know about.

Security

  • Go moves from 1.26.10 to 1.26.11: a crafted HTTP/1 request could crash the
    webhook and OAuth server through a race on the MaxBytesReader header
    (GO-2026-6859).
  • golang.org/x/net moves from 0.60.0 to 0.62.0, closing quadratic work on
    crafted HTML (GO-2026-6860); x/text and x/sync follow it.

These updates went straight into the stable version without an alpha of
their own: they change no code of Branchy's, and the full test suite and
govulncheck pass on them.

Known Limitations

  • The image was built on WS04 and pushed by hand, not by release.yml:
    GitHub Actions had not been starting for FreshLabDev since 11 November and
    came back while this release was being cut. CI passed on the tagged commit
    (the push to main); the release workflow on the tag was cancelled so it
    would not overwrite the published image.

Container image

ghcr.io/freshlabdev/branchy@sha256:faf2d848ec8f56cc717d02daf72e0b030d9416e0e9511a82ed7ce1ad0d29d848

v1.2.3-alpha.2

v1.2.3-alpha.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Oct 18:40

v1.2.3-alpha.1 was never published: CI's vulnerability scan refused it, as it
had refused every push to dev since 14 October. This cut fixes what it found.

Security

  • Go moves from 1.26.6 to 1.26.10, and golang.org/x/net from 0.57.0 to
    0.60.0, which brings golang.org/x/text 0.42.0. Together they close five
    advisories in net/http and HTTP/2 that Branchy's webhook server is exposed
    to (GO-2026-6611, -6612, -6613, -6617: a crash from an HPACK encoder race,
    connection desynchronisation after a CONNECT, flow-control and CPU abuse on
    HTTP/2 streams) and one panic on crafted input in x/text (GO-2026-6629).

Container image

ghcr.io/freshlabdev/branchy@sha256:03a9c3a049860cf8494798c84220a80676b851a978fcc079ca6a156281c04f89

v1.2.2

Choose a tag to compare

@github-actions github-actions released this 10 Sep 08:49

Branchy speaks sixteen languages.

All 173 strings it says moved out of the Go source into a translation catalogue,
the language comes from the shared hub, and there is a picker with a way back
out of a manual choice. The GitHub notification cards stay English on purpose:
one card is shared by every subscriber of a repository, so it has no single
reader whose language it could be in.

The buttons also stop contradicting themselves — the same action was two
different colours on two screens.

Changed

  • docs/releases.md names the real cause of the 403 a digest pull used to
    answer: the account running the deploy could not read the private package,
    not anything about the digest. Pulling the tag first was a workaround for
    that, and is no longer required.

v1.2.2-alpha.1

v1.2.2-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 09 Sep 20:15

Added

  • An internationalisation layer. Every string a person reads in Telegram now
    lives in internal/i18n/translations.json as key -> {lang: text} and is
    rendered through i18n.T(lang, key, pairs...), which interpolates
    {placeholder} values and falls back to English. Until now Branchy's copy was
    written inline at each point of display, which fixed the product at one
    language and made "what does this bot actually say" unanswerable without
    reading the panel code.
  • The panel surface now speaks all sixteen family languages. Every one of
    the 173 keys carries English, Russian, Ukrainian, Spanish, French, German,
    Italian, Polish, Czech, Turkish, Swedish, Belarusian, Catalan, Simplified
    Chinese, Japanese and Arabic, so a person who picked a language in voicy or
    searchy is answered in it here too, and nothing falls back. GitHub's nouns —
    repository, branch, pull request, release, webhook — follow what developers in
    each language actually write rather than what a dictionary offers, which
    differs per language and per word: French says dépôt but keeps pull request,
    German keeps Repository but says Abo, Swedish says bevakning and gren.
    The boundary is unchanged: GitHub notification cards (internal/notify) are
    still English, because one card is delivered to every subscriber of a
    repository and has no single reader whose language it could be in.
  • A Language screen on the main menu: the sixteen languages the family
    shares, in one fixed order, two per row, flag and native name. The choice is
    recorded in the shared core hub, so a language picked here answers in the
    sibling bots and one picked there answers here. Follow Telegram withdraws
    Branchy's claim instead of writing English, which is a different state:
    "answer me in English" is not "I have no opinion, use my client's".

Changed

  • Every screen is now built by one helper — bold title, italic one-line
    hint, substance in a blockquote. Screens used to assemble their own text, so
    "Repositories" was a bold line, "Choose destination" was a bold line plus a
    sentence, and "Branch filter" was a bold line and nothing else. Three screens,
    three shapes, no reason. Parts a screen does not have are not emitted, so a
    screen whose keyboard already says everything carries no empty quote.
  • Button colours mean one thing each. "Create subscription" was primary
    when reached from a repository and success when reached from the settings
    hub — the same action in two colours depending on the route in. It is
    primary in both. success is now reserved for state, and marks the option a
    single-select screen is already on (the current branch mode, the current
    release setting, the current language) rather than any action.
  • Close is painted destructive, on the group panel and on any panel opened
    from a group. It removes the panel from a conversation other people are
    reading and nothing brings that instance back. The group panel's DM link
    became its primary at the same time, so the loudest thing on it is not the
    red button.
  • The delete-confirmation screen says Back rather than "Cancel". One word
    for going up, whatever the screen.
  • Subscription validation failures now carry a translation key and its data
    rather than a finished English sentence, so the wording is chosen where the
    reader's language is known.
  • core.touch is finally handed the Telegram language_code it always had a
    parameter for. Without it, withdrawing a manual language choice would have
    fallen back to nothing at all, because the hub had never been told what the
    client asked for.

Note

GitHub notification cards are deliberately not translated. One card is
rendered once and delivered to every subscriber of a repository, frequently into
a group, so there is no single reader whose language it could be in.

v1.2.1

Choose a tag to compare

@github-actions github-actions released this 09 Sep 16:09

An About card, a group panel that can be closed, and the fix for a hole that let
any group member delete Branchy's notification cards.

Added

  • docs/releases.md gained a Deploying section, and AGENTS.md points at it.
    Releasing was documented; deploying was not, in any repository in the family —
    the process stopped at "deploy it" and never said how. That gap mattered more
    after the stacks moved from building on the host to pulling a published image,
    because the procedure changed on the same day. The section names this stack's
    host directory, its env file, the variable that selects the image, the networks
    it needs, and what a rollback actually is.

  • An About card, reachable from the main menu and from the group panel. It
    states the running version — the same string /healthz reports — plus the
    supported events, the repository, the license, and the admin contact. Until
    now nothing in the interface could answer "which version are you running",
    which is the first question any complaint has to answer. The repository is a
    link in the text rather than a second button, because two ways to reach one
    place is duplication.

  • Close on the group panel, and on the About card when it is opened from a
    group. Branchy had no way to take a panel back out of a group chat. Close acts
    only on ephemeral messages: Telegram lets a client send any callback data for
    any message it can see, so honouring close against a public message would
    have let anyone in a group delete Branchy's notification cards. There is no
    Close in DM, where the conversation is the panel and there is nothing to
    close.

  • deploy/ws04/compose.yaml, the production stack, pulling the image the
    release workflow publishes to GHCR. The stack on the host built its own image
    from a working copy, so what served users was not the artifact CI had tested,
    scanned and published, and nothing on the host could say which commit it came
    from. BRANCHY_IMAGE has no default: an unset one stops the stack instead of
    quietly starting something else.

Changed

  • One versioning and release document for the whole family. docs/versioning.md
    and docs/releases.md are now byte-identical across every Asterfield
    repository apart from two clearly marked sections: this repository's own
    version line, and the surface where a change here breaks something. They spell
    out what each of the three numbers means, what the -alpha.N suffix counts,
    when alpha becomes beta and when it is legitimate to skip to rc or run a
    pre-release in production.

  • Pre-releases are now tagged on dev, not main. Only stable versions are
    tagged on main, on the merge commit from dev. release.yml had no branch
    check at all before, so a tag pushed from any branch would publish; it now
    refuses a tag that is not on the branch its channel is published from.
    Earlier pre-releases were tagged on main under the previous rule; they are
    left as they are.

  • github.com/FreshLabDev/tg moves to v0.0.1-alpha.7. It carries one fix:
    a preflight probe is marked as a probe, so the 404 method not found it
    expects stops being counted and logged as a transport failure. All four bots
    on the shared client now run the same version.

  • The same action is now called the same thing on every screen. Three sibling
    settings screens all returned to the settings hub and each named it
    differently: the draft branch-filter screen said Done, the draft release
    screen said Back, and the draft pull-request screen flipped between the two
    depending on how many actions were selected. All three now say Back, which
    is what they do — nothing on them is committed, and the hub is the screen the
    user came from. Done survives in exactly one place, the draft branch list,
    where it skips a level rather than stepping back. Save branches on the edit
    branch list is now Save, matching the other two edit screens that commit.

  • Single-select options are marked ◉ and ◎ instead of ● and ○, the pair
    the rest of the bot family uses. Multi-select options keep ■/□, so the two
    kinds of list still cannot be confused for each other.

  • Callbacks arriving from a group are answered on the ephemeral panel itself
    (editEphemeralMessageText) rather than through editMessageText, which
    cannot address an ephemeral message. Before this, a button on the group panel
    would have left the panel frozen and answered in DM. A home callback from a
    group now returns the group panel instead of building the DM menu, which
    would have put one person's GitHub login and subscription count into a chat
    they share with everyone else. A public group message is never edited into a
    panel at all: every panel Branchy shows in a group is ephemeral, so a public
    one is a delivered notification card, and callback data can be sent for any
    visible message. Such a callback is answered in DM.

  • Both Telegram command descriptions moved out of cmd/branchy/main.go into
    internal/bot/copy.go, next to the rest of Branchy's fixed copy. Behaviour is
    unchanged — one list per scope, still all_private_chats plus an ephemeral
    all_group_chats. The file records why there is no list per language_code:
    the English-only interface is a product boundary, not missing work.

v1.2.1-alpha.2

v1.2.1-alpha.2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Sep 11:49

Release v1.2.1-alpha.2

v1.2.0

Choose a tag to compare

@github-actions github-actions released this 26 Aug 12:19

Stable Telegram Bot API 10.3 release. Promoted from v1.2.0-alpha.4 after live
production soak of title-first notification cards, in-message buttons, disabled
settings controls, and pull-request More overlays.

Added

  • GitHub notifications use Bot API 10.3 in-message action buttons
    (<tg-button-row>): Open compare / Open pull request / Open release,
    plus Copy SHA on single-commit pushes. Classic HTML fallback keeps ordinary
    links and does not include More.
  • Pull request cards include More (type="callback_data" style="link").
    Tapping it sends a separate ephemeral Rich Message to that user: a thin
    #N Title header, non-zero diff stats, and a compact File / + / − table
    loaded live from GitHub GET /repos/{owner}/{repo}/pulls/{n}/files with the
    subscription owner's OAuth token. The public card is not replaced. URL buttons
    are Open and Files.
  • Settings keyboards keep incomplete Continue, Create, Save, Done, pagination
    edges, and the current all/default/release radio visible as Bot API 10.3
    disabled buttons ({"disabled":{}}). The selected-branch radio stays
    tappable.
  • Test notifications use the same Rich HTML card chrome as live events, without
    More.

Changed

  • Notification cards are title-first: an h2 for the event (#7 Title,
    N new commits, or the release name), one quiet line for repository, action,
    branches, and author, then the body and a single trusted button row. There is
    no divider.
  • Copy is only Copy SHA on a single-commit push. Pull-request Copy #N
    and release Copy tag are gone; the release tag stays in the quiet line.
  • Long notes no longer add a second GitHub Read more / Full release notes
    link. Open pull request / Open release remain the GitHub links. Long
    flat notes fold into <blockquote expandable> with <br>; truncated or
    structured notes use <details>.
  • GFM tables are serialized with bordered striped compact.
  • PR and release bodies share the Rich Message sanitizer budget (24k HTML
    runes, 470 blocks, 13 depth, 50 media, 20 table columns, 32_768 for the whole
    card) instead of the tighter 2500/10000 source cuts.
  • Group /start replies send Bot API 10.3 ephemeral_message_parameters.
  • Classic sendMessage / editMessageText disable link previews via
    link_preview_options.

Fixed

  • Rich bodies are no longer marked truncated just because the shorter classic
    HTML fallback was cut.
  • Unclosed tg-* tags in GitHub HTML no longer swallow the rest of the body.
  • PR titles in Rich HTML are plain text when an Open button is present, so the
    card does not show two competing GitHub links.
  • Commit lists and PR subtitle lines use <p> / <br> instead of raw newlines.
  • Incomplete Done / Save branches controls stay visible as disabled buttons.
  • Test-notification fallback no longer retries classic HTML when the chat is
    permanently unreachable.

Security

  • Untrusted GitHub HTML strips tg-* tags while keeping their inner text, so
    injected in-message buttons cannot reach delivery and cannot hide later notes.
  • More lookup is scoped to destination_chat_id. Missing, foreign-chat, or
    retained-and-purged snapshots toast This snapshot expired. and do not open
    settings.
  • File patches are not stored or logged. A failed files fetch still sends the
    overlay header and toasts Could not load the file list. (or
    GitHub access expired. on GitHub 401).

Migrations

  • 009_notification_job_more.sql adds nullable more_json. Job ids are
    generated in Go so the More callback can embed m: plus a compact UUID.
    Old jobs without more_json simply have no More button.

Operations

  • Outbox payload format remains rich_html_v1. Classic HTML stays in
    notification_jobs.text as the rollback-safe fallback.
  • No new environment variables, OAuth scopes, or webhook-event requirements.
  • AUTO_MIGRATE=true applies migration 009 during upgrade from v1.1.1.
  • The webhook handler still only enqueues the job; the files API is called on
    More tap, not at webhook time.

v1.2.0-alpha.4

v1.2.0-alpha.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 26 Aug 07:31

Fourth Bot API 10.3 alpha. Long PR and release notes stay inside the folded
body; cards no longer add a second GitHub link after truncation.

Changed

  • Pull request Read more and release Full release notes links are
    gone. Long notes already collapse into <details> or an expandable quote;
    Open pull request / Open release remain the GitHub links.
  • PR and release bodies share the Rich Message sanitizer budget (24k HTML
    runes, 470 blocks, 13 depth, 50 media, 20 table columns, 32_768 for the
    whole card) instead of the tighter 2500/10000 source cuts. No new migration
    or OAuth scope.

v1.2.0-alpha.3

v1.2.0-alpha.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Aug 14:04

Third Bot API 10.3 alpha. Pull-request More shows a file diff table instead of
repeating the description.

Changed

  • The More overlay is a thin #N Title header, non-zero diff stats (including
    commit count), and a compact File / + / − table. Description, labels,
    reviewers, Commits, and Checks are gone; Open and Files remain.
  • File rows are loaded live on tap from GitHub
    GET /repos/{owner}/{repo}/pulls/{n}/files with the subscription owner's
    OAuth token. The webhook handler still only enqueues the job. New more_json
    rows omit the PR body. No new migration or OAuth scope.

Security

  • More lookup stays scoped to destination_chat_id. Patch text is not stored
    or logged. A failed files fetch still sends the overlay header and toasts
    Could not load the file list. (or GitHub access expired. on GitHub 401)
    without opening settings.