CI / Build wasm engine (push) Successful in 9m24s
The separate "publish" job had needs: build but never reused any of build's output - it re-ran the entire checkout/cache/setup/build-deps/ build/wrapper pipeline from scratch, so every tagged release did two full independent builds for no benefit. Gitea Actions doesn't support upload-artifact@v4+/download-artifact@v4+ (GHESNotSupportedError), which rules out the usual "build uploads, publish downloads" pattern anyway, so the simplest fix is to run the build pipeline exactly once and gate the three publish-only steps (version bump from tag, registry auth, npm publish) behind `if: startsWith(github.ref, 'refs/tags/')` at the step level instead of duplicating everything in a second job. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>