docs: spell out Gitea integration setup in admin Settings UI (v0.51.3)
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>
This commit is contained in:
@@ -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.
|
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
|
## 0.51.2 — 2026-07-19 12:20
|
||||||
|
|
||||||
### Fixed
|
### Fixed
|
||||||
|
|||||||
@@ -13,7 +13,13 @@ const SETTING_GROUPS = [
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
title: "Gitea Integration",
|
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,
|
keys: ["GITEA_URL", "GITEA_TOKEN", "GITEA_REPO"] as const,
|
||||||
},
|
},
|
||||||
];
|
];
|
||||||
|
|||||||
@@ -1,5 +1,5 @@
|
|||||||
// Mirrors CHANGELOG.md at the repo root — update both together.
|
// 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 = {
|
export type ChangelogEntry = {
|
||||||
version: string;
|
version: string;
|
||||||
@@ -11,6 +11,13 @@ export type ChangelogEntry = {
|
|||||||
};
|
};
|
||||||
|
|
||||||
export const CHANGELOG: 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",
|
version: "0.51.2",
|
||||||
date: "2026-07-19 12:20",
|
date: "2026-07-19 12:20",
|
||||||
|
|||||||
@@ -1,6 +1,6 @@
|
|||||||
{
|
{
|
||||||
"name": "@epicure/web",
|
"name": "@epicure/web",
|
||||||
"version": "0.51.2",
|
"version": "0.51.3",
|
||||||
"private": true,
|
"private": true,
|
||||||
"scripts": {
|
"scripts": {
|
||||||
"dev": "next dev",
|
"dev": "next dev",
|
||||||
|
|||||||
+1
-1
@@ -1,6 +1,6 @@
|
|||||||
{
|
{
|
||||||
"name": "epicure",
|
"name": "epicure",
|
||||||
"version": "0.51.2",
|
"version": "0.51.3",
|
||||||
"private": true,
|
"private": true,
|
||||||
"scripts": {
|
"scripts": {
|
||||||
"dev": "pnpm --filter web dev",
|
"dev": "pnpm --filter web dev",
|
||||||
|
|||||||
Reference in New Issue
Block a user