npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/CHANGELOG.md, branch v2.2.3

chore: bump version to v2.2.3

2026-02-27T17:29:01+00:00

Mark v2.2.2 as yanked in changelog; include annotated-tag sync regression fix in this release.

fix: skip ^{} peeled-tag refs in sync to prevent invalid refspec crash

2026-02-27T17:19:20+00:00

Regression introduced in 28ad5440: ngit sync crashed with 'invalid refspec refs/remotes/origin/v1.4.4^{}:refs/tags/v1.4.4^{}' on repos with annotated tags. Fixed by guarding all three iteration sites in sync.rs and identify_remote_sync_issues in list.rs; also corrected the always-false logic bug in invalid_nostr_state_ref.

chore: bump version to v2.2.2

2026-02-27T16:29:46+00:00

Bump Cargo.toml version to 2.2.2 and promote CHANGELOG [Unreleased] entries to [2.2.2].

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/).

feat: ngit sync --force republishes state event even with no ref changes

2026-02-27T15:53:11+00:00

allows users to repair repos whose state event is missing ^{} peeled refs for annotated tags (or any other corruption) without needing to push a new ref. the new event is signed with a fresh timestamp and broadcast to all repo relays and the user's write relays.

fix: annotated tags missing from list due to dropped peeled refs

2026-02-27T15:46:37+00:00

RepoState::try_from was explicitly discarding all refs/tags/*^{} entries ("peeled" refs) when parsing the nostr state event. This meant the list command only advertised the tag object OID, but git requires two lines for annotated tags: refs/tags/v1.0.0 refs/tags/v1.0.0^{} Without the ^{} peeled line git cannot resolve the tag to a commit, so git fetch --prune treats it as unresolvable and deletes it. The nostr state event already stores both entries correctly (written by generate_updated_state in push.rs). The fix simply stops try_from from discarding the ^{} entries on read, so they flow through to the list output unchanged.

fix: update fallback signer relays

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

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

feat: add --bunker-url to account login for non-interactive use

2026-02-27T14:24:57+00:00

allows non-interactive bunker:// URL login without requiring --nsec, by connecting to the remote signer and saving credentials to git config

feat: show and allow changing signer relays in nostrconnect flow

2026-02-27T14:24:52+00:00

display signer relays below QR code and nostrconnect URL with an option to change them via the existing multiselect UI before connecting

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").