From 4bafd5f082f5bbe35d1042d63d438c2b03d4cb21 Mon Sep 17 00:00:00 2001 From: Mathias Date: Sat, 5 Sep 2026 14:44:39 +0200 Subject: [PATCH] fix(web): views.templ imports the pre-rename gitea.d-ma.be host MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit internal/web/views.templ:7 still imports gitea.d-ma.be/mathias/tapir/internal/adapters/store while go.mod declares git.d-ma.be/mathias/tapir Left behind by the gitea rename (infra ADR-0004). The old hostname still resolves in DNS but no longer serves — HTTPS to it fails outright — so the import is genuinely broken, not merely outdated. Why nothing caught it: the COMMITTED internal/web/views_templ.go is correct, so builds and CI use a good generated file and stay green. The rot is only in the source. It surfaces the moment anyone runs `templ generate` — which regenerates the broken import over the good output, and then the build fails with no required module provides package gitea.d-ma.be/mathias/tapir/internal/adapters/store Found exactly that way while evaluating this repo for the estate-wide lint config: regenerating templ as part of the check turned a green repo red, and the cause was the source, not the check. Source fixed; regenerating now reproduces the committed generated file byte-for-byte, so views_templ.go is unchanged here. Verified: go build and go vet pass. --- internal/web/views.templ | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/web/views.templ b/internal/web/views.templ index b2d138d..602dafd 100644 --- a/internal/web/views.templ +++ b/internal/web/views.templ @@ -4,7 +4,7 @@ import ( "fmt" "strings" - "gitea.d-ma.be/mathias/tapir/internal/adapters/store" + "git.d-ma.be/mathias/tapir/internal/adapters/store" ) // Layout is the shared HTML shell. HTMX drives the progressive interactions