From d5a0ec58fc98b2bdbd15aa15bbbaf8cf7bc7e234 Mon Sep 17 00:00:00 2001 From: Devin Foley Date: Thu, 10 Sep 2026 18:54:32 -0700 Subject: [PATCH] test: retain independent cloud caller coverage Co-Authored-By: Paperclip --- server/src/__tests__/cloud-image-bundled-plugins.test.ts | 3 +++ 1 file changed, 3 insertions(+) diff --git a/server/src/__tests__/cloud-image-bundled-plugins.test.ts b/server/src/__tests__/cloud-image-bundled-plugins.test.ts index 271c4da2b5..0358db8f8b 100644 --- a/server/src/__tests__/cloud-image-bundled-plugins.test.ts +++ b/server/src/__tests__/cloud-image-bundled-plugins.test.ts @@ -78,6 +78,9 @@ describe("cloud image bundled plugins", () => { }); it("publishes the cloud image in its own job with no needs coupling", () => { + const caller = workflow.split(" build-and-push-cloud:")[1]?.split(" promote_canary_channel:")[0]; + expect(caller, "tag and manual builds must call the cloud workflow").toContain("uses: ./.github/workflows/docker-cloud.yml"); + expect(caller, "the reusable caller must also remain independent of production").not.toMatch(/^\s*needs:/m); // The reusable cloud workflow owns its job and SHA concurrency group. // Production publication must not gate, delay, or skip the cloud build. const jobsSection = cloudWorkflow.slice(cloudWorkflow.indexOf("\njobs:\n"));