From 60f4fa71ed9467cff2f50b978126160a73532c9e Mon Sep 17 00:00:00 2001 From: taylanbakircioglu Date: Thu, 9 Jul 2026 16:35:10 +0300 Subject: [PATCH] ci: read releaseName from backend/version.json in the release step (v1.8.7 follow-up) The version.json single-source move (v1.8.7) updated the version READ step but missed the create-release step, which still ran jq against the deleted repo-root version.json and failed the workflow. Point it at backend/version.json. This release step is public-only (GitHub Releases), so it has no corporate counterpart. --- .github/workflows/docker-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/docker-build.yml b/.github/workflows/docker-build.yml index a45ff54..b17f89c 100644 --- a/.github/workflows/docker-build.yml +++ b/.github/workflows/docker-build.yml @@ -81,7 +81,7 @@ jobs: run: | VERSION="${{ steps.prodversion.outputs.VERSION }}" TAG="v${VERSION}" - RELEASE_NAME=$(jq -r '.releaseName // empty' version.json) + RELEASE_NAME=$(jq -r '.releaseName // empty' backend/version.json) if gh release view "$TAG" --repo "$GITHUB_REPOSITORY" >/dev/null 2>&1; then echo "Release $TAG already exists, skipping." else