fix: pin actions/upload-artifact to v3 to ensure compatibility with Gitea
tests / python (3.10) (push) Successful in 13s
tests-macos / macos (push) Successful in 20s
tests / python (3.11) (push) Successful in 13s
tests / web (push) Successful in 38s

This commit is contained in:
Netherwarlord
2026-07-29 13:51:38 -04:00
parent d9123461dc
commit dd38181f56
2 changed files with 13 additions and 1 deletions
+6 -1
View File
@@ -56,9 +56,14 @@ jobs:
# listed, and then destroyed with the job container, so nobody can open # 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 # one. On a tag the archives reach the release instead, which is why this
# is scoped to the tagless path. # 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 - name: Upload archives for inspection
if: ${{ !startsWith(github.ref, 'refs/tags/v') }} if: ${{ !startsWith(github.ref, 'refs/tags/v') }}
uses: actions/upload-artifact@v4 uses: actions/upload-artifact@v3
with: with:
name: LM-Gambit-archives name: LM-Gambit-archives
path: dist/LM-Gambit-* path: dist/LM-Gambit-*
+7
View File
@@ -29,6 +29,13 @@ DEFAULT_ACTIONS_URL = https://github.com
Public repositories clone anonymously, so a locked or absent GitHub account does Public repositories clone anonymously, so a locked or absent GitHub account does
not affect this. Restart Gitea afterwards. 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 ## 2. Register a runner
Get a registration token from **Site Administration → Actions → Runners**, then: Get a registration token from **Site Administration → Actions → Runners**, then: