cgit, branch ch/git-2-56

git: update to v2.56.0

2026-09-30T06:39:37Z

Update to git version v2.56.0, this requires a change for this upstream commit: * 88d06b1c911e8491029ef24e96e3f412ce24c2ae pathspec: match and original in pathspec_item are const Signed-off-by: Christian Hesse Reviewed-by: John Keeping

git: update to v2.55.0

2026-09-18T17:57:35Z

Update to git version v2.55.0, this requires a change for this upstream commit: * a80a8e3ea6a070185840219778df24db832899f6 setup: stop using `the_repository` in `setup_git_directory_gently()` * ffe8005b9d8e0cf1b5d5d796ca4da76fbe219011 t: detect errors outside of test cases Signed-off-by: Christian Hesse

ui-shared: fix the Expires header on error pages

2026-09-18T11:51:15Z

page.expires is an absolute time: the normal path seeds it from page.modified and adds the relevant TTL in seconds. The error page instead assigns cache-dynamic-ttl directly, which is a count of minutes and carries no base, so every error page cgit has produced since "ui-shared: cache errors for dynamic TTL" reports Expires: Thu, 01 Jan 1970 00:00:05 GMT five seconds past the epoch, which is the value of the default TTL read as seconds. The intent of that change was to stop errors being cached forever; the effect is that they are never cached at all, since every downstream cache is told the response was already stale. Seed the value from page.modified and scale the TTL to seconds, matching what calc_ttl() does for ordinary pages. prepare_context() sets page.modified before anything can produce an error page, so the base is always available. Add a test. The header can be checked without any date arithmetic: a TTL of zero has to reproduce Last-Modified exactly, and a non-zero one has to differ from it without falling back to the epoch. Fixes: c5975ae ("ui-shared: cache errors for "dynamic TTL"") Signed-off-by: Konstantin Ryabitsev Signed-off-by: Jason A. Donenfeld

html: use buffered stdio

2026-09-18T11:48:51Z

Our generation of HTML triggers many small write(2) syscalls which is inefficient. Time output on a horrible query against my git.git mirror shows significant performance improvement: QUERY_STRING='id=2b93bfac0f5bcabbf60f174f4e7bfa9e318e64d5&id2=d6da71a9d16b8cf27f9d8f90692d3625c849cbc8' PATH_INFO=/mirrors/git.git/diff export QUERY_STRING PATH_INFO time ./cgit >/dev/null Before: real 0m1.585s user 0m0.904s sys 0m0.658s After: real 0m0.750s user 0m0.666s sys 0m0.076s Signed-off-by: Eric Wong Signed-off-by: Alyssa Ross Signed-off-by: Jason A. Donenfeld

cgit: Fix guessing default branch

2026-09-18T11:46:59Z

Even when HEAD is set to "main" in a repository, cgit still uses the "master" branch to detect the age of the last commit. Example: $ cat repositories/openwrt/openwrt.git/HEAD ref: refs/heads/main $ stat repositories/openwrt/openwrt.git/refs/heads/master Modify: 2024-02-22 23:00:01.285731731 +0000 $ stat repositories/openwrt/openwrt.git/refs/heads/main Modify: 2026-02-27 15:33:49.506017172 +0000 In this situation, cgit displays "25 months" for this repository on the index page. I guess the internal format for HEAD has changed at some point, so it needs to be taken into account when parsing it in cgit. Signed-off-by: Baptiste Jonglez Signed-off-by: Jason A. Donenfeld

css: Support for dark mode

2026-09-18T10:18:33Z

Modern browsers have a "dark mode" preference, which enables alternate styles on web sites that support this. This patch adds a dark color scheme, that is automatically activated via a CSS @media query. Older browsers that do not support color schemes will simply show the light scheme, but possibly without syntax highlighting. Note that filters that use color (such as source highlighters) and logotypes may need to be updated to work with a black background! See the updated files in the filters/ directory. Signed-off-by: Samuel Lidén Borell Signed-off-by: Jason A. Donenfeld

Bump version

2026-05-04T21:03:51Z

Signed-off-by: Jason A. Donenfeld

global: fix libc constness warnings

2026-05-04T21:03:51Z

Signed-off-by: Jason A. Donenfeld

git: update to v2.54.0

2026-05-04T17:01:20Z

Update to git version v2.54.0, this requires changes for these upstream commits: * d9ecf268ef3f69130fa269012318470d908978f6 odb: embed base source in the "files" backend * cb506a8a69c953f7b87bb3ae099e0bed8218d3ab odb: introduce "files" source ... and probably more related. Signed-off-by: Christian Hesse Signed-off-by: Jason A. Donenfeld

cgit: truncate all config values at the newline

2026-05-04T16:28:27Z

These would be largely invalid anyway (save, I suppose, for Linux file paths that technically can contain new lines). The actual problem is that these get printed back out into cached -- and trusted -- cgitrc files, and if the fields have newlines, the git-config way of less trusted users configuring repos on a shared system can be abused to inject newlines, which then can be used to smuggle global options (including filters, which execute code) into the cached cgitrc. So now, only ever duplicate up to the newline, when dealing with these inputs. Reported-by: Adrian Denkiewicz Signed-off-by: Jason A. Donenfeld