From b9fe21175f698ec0503740139f8711e68fa4a885 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20M=C3=BCller?= Date: Mon, 14 Sep 2026 12:13:38 +0000 Subject: [PATCH] :green_heart: Reuse npm cache in publish job The publish job ran npm ci against a cold cache on every release while build/maintain already share a warm node-cache key off the same lockfile. Tag runs can read caches saved on main, so wiring cache: npm here is free. --- .gitea/workflows/ci.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index afd8905..cb147a2 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -139,6 +139,10 @@ jobs: - uses: actions/setup-node@v4 with: node-version-file: .node-version + # Same lockfile/key as `build`, and tag runs can read caches + # saved on `main` — without this, every release pays a cold + # `npm ci` despite the warm shared npm cache. + cache: "npm" registry-url: "https://registry.npmjs.org/" - run: npm ci # Consume the dist/ that `build` produced and gated, instead of