Skip to content

0.26.0.1

Choose a tag to compare

@github-actions github-actions released this 27 Oct 08:18
· 112 commits to master since this release
0.26.0.1
c3c5ae8

The release 0.26.0.0 meant to be on macOS: its Apple Silicon build ran
out of memory, because the nix build compiled every hbs2 library twice.
That is fixed, and the build is about twice as fast everywhere.

It also brings the forge to the browser. hbs2-hub native-host serves
the hbs2-hub browser extension,
which shows a repository's hbs2 issues and pull requests in its GitHub
pages and can file, comment on, propose and merge them. Merging is the
new hbs2-hub pr land, which does in one step what a maintainer did
by hand: merge, push, record, publish.

Added

  • hbs2-hub native-host: the forge for a browser extension (PEP-24).
    The hub mcp tools over the browsers' native messaging, so the
    hbs2-hub browser extension
    can show and write a repository's issues and pull requests on its
    GitHub pages. Each tool runs a verb of this binary, as hub mcp
    does. A call for a repository runs in the clone named by
    git config --global hbs2-hub.<repo-key>.clone <path>, or, for a read,
    in a cache clone under ~/.cache/hbs2-hub/repos; a write never runs in
    the cache. --install writes a launcher and the host manifest for
    Firefox, Chrome and Chromium, allowing only the extension to start it;
    --uninstall removes them; --read-only offers no tool that writes.

  • hbs2-hub issue list --json and pr list --json print the index
    document (PEP-24): per thread its number, kind, id, title, status,
    applied labels, author, comment count and folded times. The
    issue_list and pr_list MCP tools return it as structured content.

  • hbs2-hub pr land: merge a pull request in one step. It merges
    the staged proposal into its target branch with a merge commit,
    computed by git merge-tree without touching the working tree, pushes
    the branch to the hbs23 remote (never forced) and to origin when
    that is a different remote, fast-forwards the local branch, records the
    merge in canon, and publishes canon. A conflict, a target branch that
    moved, or a signer that may not bless canon stops it before anything
    is pushed. --dry-run computes the merge and stops. The merge commit
    is signed when commit.gpgsign says so.

  • Writing from the browser extension (PEP-24 phases 2 and 3). The
    MCP tools issue_new, pr_new and pr_land; status --local,
    which asks no remote, and a clone object in the status document
    (the branch checked out, the remote's HEAD branch, the local branches).
    native-host signs letters as the identity hbs2-hub identity init
    wrote to git config --global.

Fixed

  • The nix build makes each library once. The shipped outputs linked
    against a second copy of every hbs2 library, built with its test suite,
    haddock and profiling, so nix build, nix profile install and the
    release jobs compiled the tree about twice; the 0.26.0.0 macOS build ran
    out of memory and never finished.

  • hbs2-hub publish and sync use the clone's hbs23:// remote, the
    one --repo is read from, instead of the remote named origin. In a
    clone kept on GitHub, with origin pointing there, publish pushed
    canon to GitHub and sync fetched it back from there. --remote
    still wins; with no hbs23 remote the default is origin, as before.

  • hbs2-hub pr show --number <n> in a clone (and the other read verbs
    in their flag form) no longer fails with "no flag claimed": the
    repository filled in from the clone goes in as --repo when the line
    is in flag form, and in front only when it is positional.

  • inbox accept of a pull request you sent yourself, from the clone
    its branch is in, still refuses (the bundle brings no commits this
    clone lacks), and now says how to accept it: from a fresh clone
    without the branch.