Update check: say what the forge answered, not zlib's "incorrect header check"

A Gitea that requires a sign-in does not refuse the branch archive: it
redirects the download to its login page, which arrives as a 200 of HTML,
and the admin page then reported zlib failing to unpack it — "incorrect
header check". Both booths showed exactly that on 29 Sept once the sign-in
requirement was switched on.

The updater now names the case: "… requires a sign-in to read
michael/ProdDash@main — turn off 'require sign-in to view' in Gitea, or
make the repo readable without one". Any other answer that is not a gzip
archive says what came back instead — a web page, or the content type —
and where to look.

tools/update-check.test.js drives the check against a mock forge: the login
redirect, a bare HTML answer, an HTTP error, and a real archive that must
still parse and be offered.

Shell 1.9.3.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

This commit is contained in:

Waters Church

2026-09-29 14:54:05 -04:00

co-authored by

Claude Fable 5.1

parent 92b98b6579

commit 601dc9e8b0

3 changed files with 190 additions and 2 deletions

									
										package.json
									
		+1
		-1
	
												View File
												
				@@ -1,6 +1,6 @@

				{

				  "name": "proddash",

				  "version": "1.9.2",

				  "version": "1.9.3",

				  "private": true,

				  "description": "Modular production dashboard for Waters Church \u2014 zero-dependency Node server + vanilla client",

				  "license": "UNLICENSED",