bircni d77e216674 fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341) ...

`exec` forwarded the toolkit's ArtifactService calls to an instance it never registered, and its random runtime token held no backend IDs, so `actions/upload-artifact` and `actions/download-artifact` v4 and later failed.

The local artifact server now serves the v4 API, including the single Put Blob uploads docker/build-push-action uses. `exec` gives each workflow its own unsigned JWT runtime token and artifact run, so artifact names conflict and carry over between runs as on GitHub. Artifacts default to a temporary directory instead of the workspace that jobs copy.

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-on: https://gitea.com/gitea/runner/pulls/1341
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com>
Co-authored-by: bircni <bircni@icloud.com>

2026-10-28 03:52:53 +00:00

..

server_test.go

fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341)

2026-10-28 03:52:53 +00:00

server_v4.go

fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341)

2026-10-28 03:52:53 +00:00

server.go

fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341)

2026-10-28 03:52:53 +00:00

token.go

fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341)

2026-10-28 03:52:53 +00:00

twirp.go

fix(exec): serve the v4 artifact API so upload-artifact v4 and later work (#1341)

2026-10-28 03:52:53 +00:00