ci(plugin-kit): quote the step name that contains a colon

`- 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.
2026-07-26 20:45:58 +02:00
parent 6e07d063c3
commit 0c261de636
1 changed files with 1 additions and 1 deletions
@@ -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.