From b4dd29893dcee1f8cff527121917ff043794ee0d Mon Sep 17 00:00:00 2001
From: Arnaud <anelissen@solem.fr>
Date: Sun, 19 Jul 2026 11:05:41 +0200
Subject: [PATCH] docs: spell out Gitea integration setup in admin Settings UI
 (v0.51.3)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

GITEA_URL/GITEA_REPO format and the exact token scope needed (issue
read+write only) were only in the commit message and CLAUDE session —
now visible right above the fields admins are filling in.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 CHANGELOG.md                         | 5 +++++
 apps/web/app/admin/settings/page.tsx | 8 +++++++-
 apps/web/lib/changelog.ts            | 9 ++++++++-
 apps/web/package.json                | 2 +-
 package.json                         | 2 +-
 5 files changed, 22 insertions(+), 4 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 419f3d4..fb0876b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,11 @@
 
 All notable changes to Epicure are documented here. This file is mirrored in-app at `/changelog` (and in the admin dashboard) via `apps/web/lib/changelog.ts` — update both together.
 
+## 0.51.3 — 2026-07-19 12:35
+
+### Fixed
+- Admin Settings' Gitea Integration section now spells out exactly what each field expects and what token scope to grant, instead of a one-line hint.
+
 ## 0.51.2 — 2026-07-19 12:20
 
 ### Fixed
diff --git a/apps/web/app/admin/settings/page.tsx b/apps/web/app/admin/settings/page.tsx
index 291b0c1..17c20dd 100644
--- a/apps/web/app/admin/settings/page.tsx
+++ b/apps/web/app/admin/settings/page.tsx
@@ -13,7 +13,13 @@ const SETTING_GROUPS = [
   },
   {
     title: "Gitea Integration",
-    description: "Support tickets submitted in-app automatically open an issue on this Gitea repo. Token needs issue read/write scope on the target repo.",
+    description:
+      "Support tickets submitted in-app automatically open an issue on this Gitea repo. Setup: " +
+      "GITEA_URL = your Gitea base URL, no trailing slash (e.g. https://git.example.com). " +
+      "GITEA_REPO = owner/repo (e.g. owner/my-app). " +
+      "GITEA_TOKEN = a personal access token — Gitea → Settings → Applications → Generate New Token — " +
+      "with the \"issue\" scope (read + write) only; nothing broader is needed since this integration " +
+      "never touches code or repo settings, just creates issues.",
     keys: ["GITEA_URL", "GITEA_TOKEN", "GITEA_REPO"] as const,
   },
 ];
diff --git a/apps/web/lib/changelog.ts b/apps/web/lib/changelog.ts
index ccf93ae..bbff0c7 100644
--- a/apps/web/lib/changelog.ts
+++ b/apps/web/lib/changelog.ts
@@ -1,5 +1,5 @@
 // Mirrors CHANGELOG.md at the repo root — update both together.
-export const APP_VERSION = "0.51.2";
+export const APP_VERSION = "0.51.3";
 
 export type ChangelogEntry = {
   version: string;
@@ -11,6 +11,13 @@ export type ChangelogEntry = {
 };
 
 export const CHANGELOG: ChangelogEntry[] = [
+  {
+    version: "0.51.3",
+    date: "2026-07-19 12:35",
+    fixed: [
+      "Admin Settings' Gitea Integration section now spells out exactly what each field expects and what token scope to grant, instead of a one-line hint.",
+    ],
+  },
   {
     version: "0.51.2",
     date: "2026-07-19 12:20",
diff --git a/apps/web/package.json b/apps/web/package.json
index aada176..6490882 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@epicure/web",
-  "version": "0.51.2",
+  "version": "0.51.3",
   "private": true,
   "scripts": {
     "dev": "next dev",
diff --git a/package.json b/package.json
index f1e5fe3..6db2db5 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "epicure",
-  "version": "0.51.2",
+  "version": "0.51.3",
   "private": true,
   "scripts": {
     "dev": "pnpm --filter web dev",