From dd38181f560c96997d78c0dd7a5b1245d0227b6e Mon Sep 17 00:00:00 2001 From: Netherwarlord Date: Wed, 29 Jul 2026 13:51:38 -0400 Subject: [PATCH] fix: pin actions/upload-artifact to v3 to ensure compatibility with Gitea --- .gitea/workflows/release.yml | 7 ++++++- packaging/GITEA-SETUP.md | 7 +++++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/release.yml b/.gitea/workflows/release.yml index dae03d5..4d03b1c 100644 --- a/.gitea/workflows/release.yml +++ b/.gitea/workflows/release.yml @@ -56,9 +56,14 @@ jobs: # listed, and then destroyed with the job container, so nobody can open # one. On a tag the archives reach the release instead, which is why this # is scoped to the tagless path. + # v3, not v4, and this is not a version to "modernise" later. From v4 the + # action refuses to run against any host that is not github.com — it + # classifies everything else as GHES and aborts with + # "GHESNotSupportedError" before uploading a byte. That is a check inside + # the action, so no amount of Gitea-side artifact support changes it. - name: Upload archives for inspection if: ${{ !startsWith(github.ref, 'refs/tags/v') }} - uses: actions/upload-artifact@v4 + uses: actions/upload-artifact@v3 with: name: LM-Gambit-archives path: dist/LM-Gambit-* diff --git a/packaging/GITEA-SETUP.md b/packaging/GITEA-SETUP.md index 9a9beb4..8d6286a 100644 --- a/packaging/GITEA-SETUP.md +++ b/packaging/GITEA-SETUP.md @@ -29,6 +29,13 @@ DEFAULT_ACTIONS_URL = https://github.com Public repositories clone anonymously, so a locked or absent GitHub account does not affect this. Restart Gitea afterwards. +**Pin `actions/upload-artifact` to v3.** From v4 the action refuses to run +against any host that is not github.com — it treats everything else as GitHub +Enterprise and aborts with `GHESNotSupportedError` before uploading anything. +The check lives inside the action, so Gitea's own artifact support is +irrelevant; v4 cannot work here at any Gitea version. The same applies to +`download-artifact`. + ## 2. Register a runner Get a registration token from **Site Administration → Actions → Runners**, then: