diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-27 15:51:01 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-27 15:53:11 +0000 |
| commit | 71cd982e5ca3e6f60fdf33fd41d0db3eabdbf39f (patch) | |
| tree | c74494e8251e876a962413e73b5b5552e4b57e51 /CHANGELOG.md | |
| parent | 28ad5440c7184de9833f8448bc90153ee4499c83 (diff) | |
feat: ngit sync --force republishes state event even with no ref changes
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.
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index f52d353..f91429b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md | |||
| @@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
| 9 | 9 | ||
| 10 | ### Added | 10 | ### Added |
| 11 | 11 | ||
| 12 | - `ngit sync --force` now republishes the state event with a fresh timestamp even when no refs have changed, allowing users to repair repos with a corrupt or incomplete state event (e.g. missing `^{}` peeled refs for annotated tags) without needing to push a new ref | ||
| 12 | - git server push option passthrough, enabling `-o secret-scanning.skip` for grasp servers | 13 | - git server push option passthrough, enabling `-o secret-scanning.skip` for grasp servers |
| 13 | - `ngit sync` now publishes the current state event to grasp server relays that are missing it or have a stale version before attempting git pushes, preventing rejections; per-relay state visibility is captured during the nostr fetch and surfaced via `FetchReport::state_per_relay` | 14 | - `ngit sync` now publishes the current state event to grasp server relays that are missing it or have a stale version before attempting git pushes, preventing rejections; per-relay state visibility is captured during the nostr fetch and surfaced via `FetchReport::state_per_relay` |
| 14 | - Fetch filters now request kind-5 deletion events for cached state and repo announcement events by `#e` tag (NIP-09), in addition to the existing `#a`-tagged filter; ensures deletions of these events are received even from clients that do not embed a repo coordinate in their deletion event | 15 | - Fetch filters now request kind-5 deletion events for cached state and repo announcement events by `#e` tag (NIP-09), in addition to the existing `#a`-tagged filter; ensures deletions of these events are received even from clients that do not embed a repo coordinate in their deletion event |