gwm 1.11.0

[1.10.0] - 2026-09-01

Added

• Ctrl+n opens the create form on an issue that already exists
(#625). gwm create --issue
(#617) derives the whole <type> <issue> <desc> triple from an issue on the
forge, and it was CLI-only. The TUI is where a worktree usually gets created,
so the one place already showing a worktree list and its linked issues was
the one place that still asked for the title to be retyped as a slug and the
branch type to be read off the labels by hand.

Ctrl+n (and create-from-issue in the command palette) opens the form on a
single field, the issue number. Enter looks the issue up rather than creating
anything; when the answer lands the form becomes the ordinary structured form
with the type, the number and the derived slug in it, and a second Enter
creates the worktree. Prefilling rather than creating is the point：the slug
is a guess about a title, and this is the surface that can show the guess
before committing to it. The derivation runs through the very functions the
CLI uses, so the two cannot produce different slugs for the same title.

Where the CLI has to refuse, the form asks. A non-interactive command has
nowhere to ask when the labels name no branch type or name two, which is what
--type is for; the form lands the cursor on the type selector with
everything else filled. A closed issue prefills with a warning rather than …

[1.9.0] - 2026-08-16

Added

The libraries compiled into the binary ship their notices
(#577). git2 builds with
vendored-libgit2 and libz-sys with static, so every binary distributed
here statically contains libgit2 and zlib, and no package dependency carries
their terms. libgit2 is GPLv2 with a linking exception, and that
exception is what makes a permissively licensed binary possible at all: it
is conditional on the notice travelling with the distribution. zlib's terms
say its notice may not be removed. Neither was shipping, and neither had
anything to do with the project's own license, which is why this is separate
from #573 rather than part of it: both were unmet under MIT-only too.

Both notices now live under third-party/ and reach the release archives,
the .deb, the .rpm, the AUR package and the published crate. They are
taken from the crate source cargo actually built, not from the libraries'
upstream repositories, because those diverge: libgit2-sys vendors a pinned
tree while libgit2 main moves.

third-party/README.md records which crate version each came from, and that
record is checked against Cargo.lock. A dependency bump moves the vendored
library without touching a file anyone reads, so without the check the notice
would quietly go on describing a version the binary no longer contains.

Changed
…