Fix #513 (reopened): unconditional ~k suffix #516

Merged
crueber merged 1 commit from fix/issue-513-etag into main 2026-09-14 14:22:41 +00:00
Owner

Reopened #513: the Checks tab stayed visible because the ~k ETag suffix was conditional on checksOK — a zero-check repo's ETag was byte-identical to its pre-#505 ETag, so cached summaries 304-matched forever and never received has_checks (fail-open → tab shown). This change makes ~k unconditional (~k0 when absent; present indexes are always Version >= 1, so no collision). Includes the regression test (bare-sha pre-#505 ETag must 200), updated ETag pins across the api suite, and doc amendments. api 95.3%, -race clean.

Reopened #513: the Checks tab stayed visible because the ~k ETag suffix was conditional on checksOK — a zero-check repo's ETag was byte-identical to its pre-#505 ETag, so cached summaries 304-matched forever and never received has_checks (fail-open → tab shown). This change makes ~k unconditional (~k0 when absent; present indexes are always Version >= 1, so no collision). Includes the regression test (bare-sha pre-#505 ETag must 200), updated ETag pins across the api suite, and doc amendments. api 95.3%, -race clean.
Sign in to join this conversation.
No description provided.