From 231e0c708b3f06c1abc3fae22d7a48cc7a7b1894 Mon Sep 17 00:00:00 2001
From: npeter83 <npeter83+claude@gmail.com>
Date: Sun, 21 Jun 2026 07:07:56 +0200
Subject: [PATCH] =?UTF-8?q?chore:=20release=200.14.1=20=E2=80=94=20finish?=
 =?UTF-8?q?=20subfeed=E2=86=92siftlode=20rename?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Bump VERSION and add a release-notes entry for the rename cleanup so the
prod image is published under a fresh tag rather than overwriting 0.14.0.
---
 VERSION                          | 2 +-
 frontend/src/lib/releaseNotes.ts | 9 +++++++++
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/VERSION b/VERSION
index a803cc2..930e300 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.14.0
+0.14.1
diff --git a/frontend/src/lib/releaseNotes.ts b/frontend/src/lib/releaseNotes.ts
index d19e12e..72a6abd 100644
--- a/frontend/src/lib/releaseNotes.ts
+++ b/frontend/src/lib/releaseNotes.ts
@@ -14,6 +14,15 @@ export interface ReleaseEntry {
 }
 
 export const RELEASE_NOTES: ReleaseEntry[] = [
+  {
+    version: "0.14.1",
+    date: "2026-06-21",
+    summary:
+      "Internal cleanup: the project's original working name was fully retired in favour of Siftlode.",
+    chores: [
+      "Renamed the last remaining references to the project's original codename throughout the codebase, deployment config and database identity. No behavioural change. One side effect: locally remembered view preferences (theme, feed filters, dismissed hints) reset to their defaults once, because the browser-storage keys were renamed too.",
+    ],
+  },
   {
     version: "0.14.0",
     date: "2026-06-21",