npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/src/lib, branch v2.2.1Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/atom?h=v2.2.12026-02-25T12:27:56+00:00fix: update hardcoded libgit2 version strings in tests to 1.9.22026-02-25T12:27:56+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-25T12:27:56+00:00urn:sha1:ca2df272594a7b055c740ccda0b9c31b3b7e43cc
The Nix environment provides libgit2 1.9.2 via nixpkgs, which
libgit2-sys picks up at build time instead of using its bundled version.
This caused test assertions that hardcode the libgit2 version string
(appended by libgit2 to patch output) to fail after commit 319bb7f
added new Cargo dependencies, though the exact mechanism by which those
dependencies triggered the switch from the bundled 1.9.1 to the system
1.9.2 remains unclear.
Also bump git2 from 0.20.2 to 0.20.4 in both Cargo.toml files so the
bundled libgit2-sys version (0.18.3+1.9.2) properly aligns with the
1.9.2 version in use.
fix IPv6 connection failures with Happy Eyeballs (RFC 8305)2026-02-25T11:48:13+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-25T11:21:45+00:00urn:sha1:319bb7fa2c984da45422fa81d12b4a5226beb493
Implement a custom WebSocketTransport that races IPv6 and IPv4 connections
with a 250ms head start for IPv6, matching browser behavior. This prevents
broken IPv6 from blocking all relay connections indefinitely.
This is a temporary fix until the upstream async-wsocket PR is merged:
https://github.com/shadowylab/async-wsocket/pull/42
improve `ngit repo` output formatting2026-02-20T22:41:50+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T22:41:50+00:00urn:sha1:68779f91f051822270f156a4185350fb3c4b5017
- suppress fetch summary (no updates / updates: X)
- write blank line to stderr after relay errors for clear separation
- show identifier below title only when it differs from name
- show earliest unique commit (root_commit) in metadata
- restructure infrastructure into grasp servers / additional git
servers / additional relays sections
- display grasp servers by domain only (strip scheme, npub, repo path)
- strip wss:// prefix from relay display
- show maintainer names from metadata cache; fall back to short npub
- append (you) next to the current user's name wherever it appears
- show [name] attribution and the maintainer model note only when
there is more than one maintainer
replace nos.lol with relay.ditto.pub as default relay2026-02-20T21:21:54+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T21:18:27+00:00urn:sha1:67f09343c15e6a0e3622811d3eb5e513a8205eda
nos.lol always prompts for nip42 auth even for reading, making it
unsuitable as a default relay.
use trusted maintainer's grasp servers as fallback for co-maintainers2026-02-20T21:21:52+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T21:14:45+00:00urn:sha1:b10340cb00a00da07d0ae735796d83801454779e
when a co-maintainer has no grasp servers of their own, fall back to
the trusted maintainer's grasp servers rather than jumping straight to
system defaults. if the trusted maintainer only uses a single grasp
server, the first system default is appended for redundancy. system
defaults are only used when neither the user nor the trusted maintainer
has any grasp servers configured.
default relay prompt to no selection; add is never pre-selected2026-02-20T21:21:51+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:35:13+00:00urn:sha1:fa99cf7dfc9e6b16e67afe03873486039263ce42
With no default relays seeded, the multi-select add option was
incorrectly pre-selected when the list was empty. Now add/add-another
is always unselected by default so enter skips straight through.
drop default relays from announcement events2026-02-20T21:21:49+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:26:31+00:00urn:sha1:724e02ac8c538e9dfe4faa072082fad301e49b10
ngit init and accept_maintainership_with_defaults no longer seed relay
lists from the client default set. The relay list in a Kind:30617
announcement now contains only grasp-server-derived relay URLs; no
additional public relays are suggested or added automatically.
extract grasp/maintainership helpers to lib and auto-accept on push2026-02-20T21:21:48+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-20T20:09:09+00:00urn:sha1:64747526c9f6ab43f9dac461d056bb42992573b4
move apply_grasp_infrastructure, latest_event_repo_ref to lib/repo_ref.rs
and wait_for_grasp_servers + grasp_servers_from_user_or_fallback to a
new lib/accept_maintainership.rs so both binaries can share them.
add accept_maintainership_with_defaults which publishes the co-maintainer's
own Kind:30617 announcement with defaults (user grasp servers, shared
metadata from existing events) then waits for grasp server provisioning
and updates nostr.repo config and origin remote.
replace the push error block with a call to accept_maintainership_with_defaults
so pushing now silently accepts co-maintainership instead of failing.
fix: remove outdated patch_supports gate and fix fetch parent fallback2026-02-18T22:00:35+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T22:00:35+00:00urn:sha1:56b3c149df70af5d441e8527ec1225e5038bde8e
Remove the patch_supports_commit_ids gates in checkout.rs and list.rs
that pre-dated the mbox fallback logic. apply_patch_chain already
handles all fallback cases. Also replace the main-branch TODO fallback
in make_commits_for_proposal with get_parent_commit_from_patch, which
uses timestamp-based best-guess when the parent-commit tag is absent.
fix: thread applied OID through patch chain correctly2026-02-18T21:17:41+00:00DanConwayDevDanConwayDev@protonmail.com2026-02-18T21:17:41+00:00urn:sha1:09db17fd719ddd42c5afad24e1a8e71735374f8e
When applying a chain of patches without parent-commit tags, each
patch's parent was resolved independently, meaning patch2 would not
parent off the OID patch1 actually produced. Thread next_parent_override
through the loop and guard the early-return in create_commit_from_patch
so the override is always honoured.