From 0c261de636f5fc64502223aee07ee5861674fe01 Mon Sep 17 00:00:00 2001 From: enricobuehler Date: Sun, 26 Jul 2026 20:45:58 +0200 Subject: [PATCH] ci(plugin-kit): quote the step name that contains a colon MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `- name: Repair the file: dependency (…)` is not valid YAML — the unquoted `file: ` reads as a second mapping key — so the workflow has been unparseable since it was added, which is why re-pushing the tag never triggered a run and a manual dispatch 500'd. I had put that down to a Gitea tag quirk; it was this. The failure is invisible from the repo side: nothing validates workflow YAML on push, and an unparseable workflow simply never runs. --- .gitea/workflows/plugin-kit-publish.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/plugin-kit-publish.yml b/.gitea/workflows/plugin-kit-publish.yml index 14bddc54..0e0e7271 100644 --- a/.gitea/workflows/plugin-kit-publish.yml +++ b/.gitea/workflows/plugin-kit-publish.yml @@ -45,7 +45,7 @@ jobs: # it does not, so module resolution dies at the first step and every `@punktfunk/host` import # reads as "cannot find module". Replacing the tree with a real copy is the whole fix; drop # this step once bun links `file:` deps correctly again. - - name: Repair the file: dependency (bun 1.3 self-symlink) + - name: "Repair the file: dependency (bun 1.3 self-symlink)" working-directory: plugin-kit run: | # -f follows the link, so this is true only when the manifest actually resolves.