From 98413d860472fcd206c12cf6365a8aa47ea44bae Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Fri, 16 Oct 2026 22:19:44 -1000 Subject: Claim and test Lua 5.5 for every extension luaossl from release 20260910 and luaposix load under Lua 5.5, and cgit renders the same pages under it as under LuaJIT. Running the suites there already caught a write to a for loop's control variable, which 5.5 makes read-only. --- custom/extensions/auth-file.lua | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'custom/extensions/auth-file.lua') diff --git a/custom/extensions/auth-file.lua b/custom/extensions/auth-file.lua index dc21bec..354adac 100644 --- a/custom/extensions/auth-file.lua +++ b/custom/extensions/auth-file.lua @@ -7,9 +7,9 @@ -- maintained by something else. The companion auth-inline.lua behaves -- identically but carries the same lists inside the script. --- The script runs on Lua 5.1, 5.2, 5.3, 5.4 and LuaJIT, and the runtime has to --- be the same Lua that cgit was built against. Lua 5.5 will not do, because --- luaossl has no 5.5 build. +-- The script runs on Lua 5.1 through 5.5 and LuaJIT, and the runtime has to be +-- the same Lua that cgit was built against. On 5.5 it needs luaossl 20260910 +-- or later, since earlier builds fail to load there. -- -- The session cookie is marked Secure by default, so a browser only sends -- it back over HTTPS. On an instance served over plain HTTP login loops -- cgit