From dc920a3e545e544f68fb7bc983f181803b56fb47 Mon Sep 17 00:00:00 2001
From: Foowy <49217685+Foowy@users.noreply.github.com>
Date: Sun, 16 Aug 2026 09:30:00 +0000
Subject: [PATCH] fix(workflows): force-push the release tag on nuget publish
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

#1405's tag_exists_error: false never took effect: action-create-tag's
existence check is git tag -l, a local check, but the daily-build
runner does a fresh checkout with no tags fetched — it always sees
'not exists' locally and tries to create+push the tag fresh, which the
remote then rejects since the tag is already there. force_push_tag
force-pushes unconditionally, which is a no-op when the tag already
points at the same commit.
---
 .github/actions/publish-nuget/action.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/actions/publish-nuget/action.yml b/.github/actions/publish-nuget/action.yml
index f0769a812..c32b99464 100644
--- a/.github/actions/publish-nuget/action.yml
+++ b/.github/actions/publish-nuget/action.yml
@@ -47,4 +47,4 @@ runs:
       with:
         tag: ${{ steps.version.outputs.tag }}
         message: "${{ inputs.project-file-path }} v${{ steps.version.outputs.version }}"
-        tag_exists_error: false
+        force_push_tag: true