From 1097cb425c84cedcdc315954700d6cee59c4253b Mon Sep 17 00:00:00 2001 From: nmemmert Date: Wed, 26 Aug 2026 13:53:37 -0400 Subject: [PATCH] Fix docker-compose to use Gitea registry image; v1.1.41 docker-compose.yml was still pointing to the old GHCR image (ghcr.io/nmemmert/siteforge:latest) after CI was switched to push to git.necloud.us/nate/siteforge:latest, so servers were pulling a stale build that predated the download/header changes. Co-Authored-By: Claude Sonnet 4.6 --- docker-compose.yml | 2 +- package.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index ec48419..81b3854 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -1,6 +1,6 @@ services: portfolio: - image: ghcr.io/nmemmert/siteforge:latest + image: git.necloud.us/nate/siteforge:latest pull_policy: always container_name: siteforge-app ports: diff --git a/package.json b/package.json index 1f2c3be..ceeea61 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "siteforge", "private": true, - "version": "1.1.40", + "version": "1.1.41", "type": "module", "scripts": { "dev": "vite",