From c1464228dfd273960ed261c43a8e7212ef57b4b2 Mon Sep 17 00:00:00 2001 From: bvandeusen Date: Fri, 31 Jul 2026 23:44:29 -0400 Subject: [PATCH] docs: Fabled-Git, not Forgejo, where the instance is meant MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Four references to "Forgejo" actually meant this instance, which has run Gitea since the migration: the registry push, the missing /releases/latest/download route, the API a packaging script resolves URLs against, and the 422 on an illegal JSON escape. Kept as-is — these are genuinely about the upstream Forgejo project, not us: the `forgejo/upload-artifact` mirror and "the Forgejo project's fork". Prose only — no workflow, path, or script change. Scribe issue #2272. --- ci-requirements.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ci-requirements.md b/ci-requirements.md index 0165888..c7d3f4d 100644 --- a/ci-requirements.md +++ b/ci-requirements.md @@ -23,7 +23,7 @@ build (docker buildx). - ruff — lint job runs `ruff check src/` with zero install overhead - uv — test job creates the venv (`uv venv /opt/venv`) and installs the package with dev deps -- docker CLI + buildx — build job pushes the dev/release image to the Forgejo +- docker CLI + buildx — build job pushes the dev/release image to the Fabled-Git registry ## Per-job tool installs @@ -188,7 +188,7 @@ error: src refspec dev matches more than one ``` The rolling update channel is a release on a **fixed tag named `dev`** (the tag -never moves — Forgejo has no `/releases/latest/download/` route, so the +never moves — Fabled-Git has no `/releases/latest/download/` route, so the updater needs a permanent URL). Once that tag is fetched locally, the short name `dev` resolves to both `refs/heads/dev` and `refs/tags/dev`. Fully qualify it: @@ -207,15 +207,15 @@ dash -n desktop/packaging/install.sh # or: sh -n bash -n desktop/packaging/publish-release.sh ``` -Where a script resolves URLs from the Forgejo API, exercise the resolution +Where a script resolves URLs from the Fabled-Git API, exercise the resolution against the live instance (plain `curl` reads, no install) rather than trusting the regex by eye. Both channel paths in `install.sh` were verified that way. **Hand-assembled JSON: parse it before you push it.** `publish-release.sh` builds its request bodies as shell strings, and quoting context decides what survives -into the JSON — a `` \` `` inside an unquoted heredoc loses its backslash to the -shell, the same `` \` `` inside a single-quoted variable does not, and reaches -Forgejo as an illegal escape (HTTP 422, one wasted build). `sh -n` cannot see +into the JSON — a `` \ `` inside an unquoted heredoc loses its backslash to the +shell, the same `` \ `` inside a single-quoted variable does not, and reaches +Fabled-Git as an illegal escape (HTTP 422, one wasted build). `sh -n` cannot see this. Extract the body block and parse it for every branch it can take: ```