Can token lifetime for actions be a configurable thing? #35230
Description
Description
Hi!
We are building a CI/CD pipeline with rather long running actions, longer that 24h at least.
The invalidated token will produce a http 500 error when uploading the artifact with a final upload-artifact step on the workflow. From giteas server log:
2025/08/01 13:45:44 .../actions/artifacts.go:164:ArtifactsRoutes.ArtifactContexter.2.1() [E] Error runner api getting task: task with token "<token>": resource does not exist
2025/08/01 13:45:44 HTTPRequest [I] router: completed POST /api/actions_pipeline/_apis/pipelines/workflows/473/artifacts?api-version=6.0-preview for <runner_ip>:0, 500 Internal Server Error in 0.2ms @ actions/artifacts.go:127(actions.ArtifactsRoutes.ArtifactContexter)
Is there a reason against making this configurable somehow or is that nothing we should run on the pipeline for reasons I am not seeing yet?
For reference, this is one of the runs that has the problem: https://git.crux.nu/system/crux-rootfs/actions/runs/166
Gitea Version
1.24.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.49.0
Operating System
CRUX
How are you running Gitea?
Self compiled Gitea and started by a rc file (sysvinit system).
Database
PostgreSQL