take the artifact action from a fork of our own (#10)

Upstream v4 refuses to run anywhere but github.com: it reads
GITHUB_SERVER_URL, calls everything else a GitHub Enterprise Server and
throws before making a request. A probe run settled the rest — the name
cannot be overridden from a step, because the runner sets the GITHUB_
ones last. So the action now comes from this Gitea, forked with that one
check removed, on a fixed tag rather than a floating one.

Reviewed-on: #10
Co-authored-by: Aleksandr Neychev <alexnejchev73@gmail.com>

.gitea/workflows/release.yml

@@ -138,9 +138,22 @@ jobs:
       - name: Build the installer
         run: ./Packaging/build-installer.ps1 -Version ${{ steps.version.outputs.plain }}
 
-      # The artifact is where the package waits to be uploaded to Partner Center
+      # The artifact is where the package waits to be uploaded to Partner Center.
+      #
+      # The action comes from this Gitea rather than from github.com, and it is
+      # a fork of actions/upload-artifact with one line changed. Upstream reads
+      # GITHUB_SERVER_URL, takes every host but github.com and its enterprise
+      # ones for a GitHub Enterprise Server — where the v4 artifact backend does
+      # not exist — and throws before it makes a request. Here that backend does
+      # exist and answers, but the check runs on the runner ahead of the network
+      # and never lets it prove itself; nor can the name be corrected from this
+      # file, as the runner sets the GITHUB_ ones over the env of a step. The
+      # fork carries the reasoning in full in its GITEA-PATCH.md.
+      #
+      # The tag is a fixed one. A floating tag is how this broke before: the
+      # action is fetched at run time, and what arrives can change on its own
       - name: Keep the package
-        uses: actions/upload-artifact@v4
+        uses: https://git.alrakis.kz/actions/upload-artifact@v4-gitea
         with:
           name: msix-${{ steps.version.outputs.version }}
           path: artifacts/packages/
@@ -149,7 +162,7 @@ jobs:
       # The .wixpdb next to each installer is left out on purpose: it is of use
       # only when something has to be traced back to the WiX source
       - name: Keep the installer
-        uses: actions/upload-artifact@v4
+        uses: https://git.alrakis.kz/actions/upload-artifact@v4-gitea
         with:
           name: installer-${{ steps.version.outputs.plain }}
           path: artifacts/installers/*.msi
@@ -167,10 +180,8 @@ jobs:
 
           # The GITHUB_ names are what Gitea itself hands to the workflow — its
           # actions repeat those of GitHub, and the addresses in them point at
-          # this Gitea instance. GITHUB_API_URL used not to reach the steps at
-          # all, so the address is put together from the server one when empty
-          $root = if ($env:GITHUB_API_URL) { $env:GITHUB_API_URL } else { "$env:GITHUB_SERVER_URL/api/v1" }
-          $api = "$root/repos/$env:GITHUB_REPOSITORY/releases"
+          # this Gitea instance
+          $api = "$env:GITHUB_API_URL/repos/$env:GITHUB_REPOSITORY/releases"
           $headers = @{ Authorization = "token $env:GITEA_TOKEN" }
 
           # Gitea makes a release of its own for a pushed tag, so the release is