diff --git a/argocd/manifests/shower/kustomization.yaml b/argocd/manifests/shower/kustomization.yaml
index 6fe641f..b6de844 100644
--- a/argocd/manifests/shower/kustomization.yaml
+++ b/argocd/manifests/shower/kustomization.yaml
@@ -14,4 +14,4 @@ resources:
 
 images:
   - name: registry.ops.eblu.me/blumeops/shower
-    newTag: v1.1.0-444ff91-nix
+    newTag: v1.1.0-3c7967e-nix
diff --git a/docs/changelog.d/+shower-rebuild-from-main-sha.misc.md b/docs/changelog.d/+shower-rebuild-from-main-sha.misc.md
new file mode 100644
index 0000000..a9495cd
--- /dev/null
+++ b/docs/changelog.d/+shower-rebuild-from-main-sha.misc.md
@@ -0,0 +1,6 @@
+Rebuild shower v1.1.0 container from main HEAD (`3c7967e`) and bump the
+kustomization tag to `v1.1.0-3c7967e-nix`. The PR was squash-merged, so
+the branch commit `444ff91` baked into the prior tag isn't reachable
+from main's history. The new tag points at a commit that exists on
+main; image content is byte-identical because the FOD output is content
+addressed and the inputs didn't change.