5 Commits (fcbbc24cc43811f2fc2f99b2f88060bc360ec38f)

Author	SHA1	Message	Date
TheFox0x7	33e8e82c4b	Enable tenv and testifylint rules (#32852) ... Enables tenv and testifylint linters closes: https://github.com/go-gitea/gitea/issues/32842	2 months ago
silverwind	c77e8140bc	Add `interface{}` to `any` replacement to `make fmt`, exclude `*.pb.go` (#30461) ... Since https://github.com/go-gitea/gitea/pull/25686, a few `interface{}` have sneaked into the codebase. Add this replacement to `make fmt` to prevent this from happening again. Ideally a linter would do this, but I haven't found any suitable.	10 months ago
ChristopherHX	368743baf3	Add ac claim for old docker/build-push-action@v3 / current buildx gha cache (#29584) ... Also resolves a warning for current releases ``` | ##[group]GitHub Actions runtime token ACs | ##[warning]Cannot parse GitHub Actions Runtime Token ACs: "undefined" is not valid JSON | ##[endgroup] ====> | ##[group]GitHub Actions runtime token ACs | ##[endgroup] ``` \* this is an error in v3 References in the docker org: - 831ca179d3/src/main.ts (L24) - 7d8b4dc669/src/github.ts (L61) No known official action of GitHub makes use of this claim. Current releases throw an error when configure to use actions cache ``` | ERROR: failed to solve: failed to configure gha cache exporter: invalid token without access controls | ##[error]buildx failed with: ERROR: failed to solve: failed to configure gha cache exporter: invalid token without access controls ```	11 months ago
wxiaoguang	8be198cdef	Use general token signing secret (#29205) ... Use a clearly defined "signing secret" for token signing.	12 months ago
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>	1 year ago