Fix CI: drop upload-artifact (unsupported on Gitea, unused downstream)
CI / Publish to npm registry (push) Canceled after 0s
CI / Build wasm engine (push) Canceled after 36s

actions/upload-artifact@v4+ refuses to run on Gitea (it's detected as
GHES, and v4's new backend API explicitly isn't supported there -
GHESNotSupportedError). Rather than pin back to the last GHES-compatible
v3.2.2, just remove the step: the publish job doesn't consume this
artifact - it does its own independent checkout+build - so it was only
ever a convenience for manually downloading dist/ from a CI run, not
something the pipeline depends on.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-22 18:34:09 +02:00
co-authored by Claude Sonnet 5
parent 4f4c2b6b91
commit d22dc28af3
-5
View File
@@ -72,11 +72,6 @@ jobs:
npm install --no-save typescript npm install --no-save typescript
npx tsc -p package/tsconfig.json npx tsc -p package/tsconfig.json
- uses: https://github.com/actions/upload-artifact@v4
with:
name: vpinball-wasm-dist
path: dist/
publish: publish:
name: Publish to npm registry name: Publish to npm registry
if: startsWith(github.ref, 'refs/tags/') if: startsWith(github.ref, 'refs/tags/')