Artifact 8353970203d6aa59d78cf2037f035d2a3368fe33fad65ce2cf0c4cb876ab03f6:
- File
src/sync_test.zig
-
2026-08-26 16:57:06
— part of check-in
[13760d0c92]
on branch serve-protected-branches
— serve: refuse a check-in's own singleton claim on a protected name; warm the image only after a push
A self-targeted +sym-B is not how a branch is joined, but nothing legitimate mints one on a protected name. maintain now derives the fast-read image only when the log grew, so a pull-heavy fronted server does not pay an image load per connection. Pins that a merge with a protected secondary parent stays on its primary's branch. Issue #151. (user: dmestas, size: 492060) [annotate] [blame] [check-ins using]
- 2026-08-26 19:43:30 — part of check-in [d46cb9a855] on branch trunk — merge serve-protected-branches: per-request branch protection behind a trusted front (#151) (user: dmestas, size: 492060) [annotate] [blame] [check-ins using]
-
2026-08-26 16:57:06
— part of check-in
[13760d0c92]
on branch serve-protected-branches
— serve: refuse a check-in's own singleton claim on a protected name; warm the image only after a push