npub1sh4dwqc9ypguemh6m8tmxxl8xuzfsz0j8av8vq7t3xd3mldsg9ls4ew80h/ngit-cli-mirror/src/lib/client.rs, branch v2.2.3

fix: include KIND_PULL_REQUEST IDs in proposal_ids for fetch filters

2026-02-27T16:11:36+00:00

kind-5 deletion events that only #e-tag a PR Kind event (kind 1618) were never fetched because proposal_ids was built from Kind::GitPatch events only. The deleted PR event remained in the local cache and continued to appear as a remote ref (refs/heads/pr/).

fix: update fallback signer relays

2026-02-27T14:26:48+00:00

Replace nsec.app with bucket.coracle.social and nos.lol.

feat: track and display kind-5 deletion count in FetchReport

2026-02-26T21:13:29+00:00

Add a deletions counter to FetchReport, incremented in process_fetched_events for each kind-5 event received and accumulated across relays in consolidate_fetch_reports. The count is included in the fetch summary display (e.g. "1 deletion", "2 deletions").

feat: request kind-5 deletions for state/announcement events by #e

2026-02-26T21:12:27+00:00

Add a non_proposal_event_ids parameter to get_fetch_filters and a corresponding field on FetchRequest. On each fetch, the event IDs of cached repo announcements and the state event are collected and used to build a dedicated kind-5 filter keyed on #e tags, as specified by NIP-09. The existing #a-tagged filter already covers addressable-event deletions; this new filter catches deletions from clients that follow NIP-09 strictly and do not embed a repo coordinate in their deletion event.

fix: show detailed relay view when --verbose flag is set in send_events

2026-02-26T15:26:21+00:00

The use_concise flag in send_events was computed with || instead of &&, causing !is_test to short-circuit to true in production and making --verbose have no effect on published event display.

feat: publish state event to stale grasp relays before sync push

2026-02-26T15:26:18+00:00

FetchReport now captures the full state event seen on each relay during the nostr fetch (state_per_relay: HashMap>). ngit sync uses this to identify grasp server relays with a missing or outdated state event and publishes the current state event to them before attempting git pushes, preventing rejections. An existing login is loaded silently (no prompt, no profile fetch) to provide a signer for NIP-42 auth if requested.

fix: rollback local state event cache on total push failure

2026-02-26T15:26:18+00:00

When all git servers reject or skip a push, delete the newly-published state event from the local nostr cache and restore the previous state event (if any), so that a subsequent retry starts from a clean baseline rather than a state that no server ever accepted.

fix: report per-relay publish results in send_events summary

2026-02-26T15:26:16+00:00

Change send_events() return type from Result<()> to Result> so callers can inspect which relays accepted events. Update the finish message to show "Published to X/N relays (failed: ...)" instead of the unconditional "Published ... to nostr relays".

fix IPv6 connection failures with Happy Eyeballs (RFC 8305)

2026-02-25T11:48:13+00:00

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 formatting

2026-02-20T22:41:50+00:00

- 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