From 25297cbea032d725e9687541939cfffeabf79dfb Mon Sep 17 00:00:00 2001 From: Joris Wouter Jonkers Date: Tue, 27 Oct 2026 16:12:46 +0100 Subject: [PATCH] fix(deploy): validate the project file with its env files when publishing On deploy-kit 1.0 the auth-api Process's transit grant needs the Vault client its env file wires (${identity:vaultRole}). Publish Fragment validated the project file alone, so the v0.21.0 fragment was refused with E_SELF_WITHOUT_VAULT_CLIENT and never published. Part of #119 --- .github/workflows/publish.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index aef801c..2492267 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -210,6 +210,8 @@ jobs: uses: JorisJonkers-dev/github-workflows/.github/workflows/publish-fragment.yml@16d241e44f03c5cc4696d2d0de615717a61ef3c0 # v0.36.0 with: project-file: deploy/auth.project.yml + # The env files wire the Vault client the transit grant needs. + validate-with: deploy/env version: ${{ github.ref_name }} images-lock-artifact: ${{ needs.resolve-image-lock.outputs.fragment-images-lock-artifact }} secrets: