ChristopherHX a9bc590d5d Add artifacts v4 jwt to job message and accept it (#28885) ... This change allows act_runner / actions_runner to use jwt tokens for `ACTIONS_RUNTIME_TOKEN` that are compatible with actions/upload-artifact@v4. The official Artifact actions are now validating and extracting the jwt claim scp to get the runid and jobid, the old artifact backend also needs to accept the same token jwt. --- Related to #28853 I'm not familar with the auth system, maybe you know how to improve this I have tested - the jwt token is a valid token for artifact uploading - the jwt token can be parsed by actions/upload-artifact@v4 and passes their scp claim validation Next steps would be a new artifacts@v4 backend. ~~I'm linking the act_runner change soonish.~~ act_runner change to make the change effective and use jwt tokens <https://gitea.com/gitea/act_runner/pulls/471>		2024-02-02 14:25:59 +00:00
..
ping	Implement actions (#21937)	2023-01-31 09:45:19 +08:00
runner	Add artifacts v4 jwt to job message and accept it (#28885)	2024-02-02 14:25:59 +00:00
actions.go	Refactor web package and context package (#25298)	2023-06-18 09:59:09 +02:00
artifacts_chunks.go	Fix uploaded artifacts should be overwritten (#28726)	2024-01-17 11:21:16 +08:00
artifacts_utils.go	Fix/upload artifact error windows (#27802)	2023-10-30 10:40:05 +00:00
artifacts.go	Add artifacts v4 jwt to job message and accept it (#28885)	2024-02-02 14:25:59 +00:00