5 Commits

Include renames

Author	SHA1	Message	Date
BenVandZettat123	c344004e53	fix(actions): settle cancelled reusable workflow runs stuck in cancelling (#39706) ... Fixes #39702 **Root Cause:** Cancelling a reusable workflow caller wrote it `cancelled` right away, even while a child was still `cancelling`. When the runner acknowledged, the caller did not change, so the run was never refreshed and stayed `cancelling`. SQLite hid this because the child is cancelled a second time, which re-aggregates the caller, while MySQL reports no affected rows for that unchanged update. **Changes:** - A caller now takes its status only from its children: it stays `cancelling` until its last child finishes, and its final status then refreshes the run. - Cancelling a run whose jobs are all done only settles the run, which did not wake the runs waiting for its concurrency group. It now does, so force-cancelling an already stuck run also frees them. --------- Signed-off-by: BenV <165034+benv666@users.noreply.github.com> Co-authored-by: Zettat123 <zettat123@gmail.com>	2026-10-10 09:46:57 +02:00
silverwind	f757631a47	feat(actions): update actionslib, support self:, misc fixes (#39358) ... Updates actionslib to https://gitea.com/gitea/actionslib/releases/tag/v1.2.1, moves workflow parsing into it and aligns behaviour with GitHub. 1. `uses:` supports `self:` (Gitea-only feature) and `$/` paths. 1. `strategy`, `matrix`, `max-parallel` and `fail-fast` accept expressions, including over `needs`. A job whose `name`, `runs-on` or `continue-on-error` reads `needs` is resolved once they finish. 1. A job `if:` may only read `github`, `needs`, `vars` and `inputs` and is decided before the matrix, as on github.com. 1. Matrix `fail-fast` cancels the other combinations, and `always()` jobs keep running when a run is cancelled. 1. Invalid workflow files, including a malformed `on:` and unknown or cyclic `needs`, show up on push as failed runs with the error. 1. A job whose `if:` or `concurrency:` fails to evaluate is skipped or failed with the error, instead of staying blocked. 1. Reusable workflows: a missing and an unreadable repository fail alike, public callers cannot use private workflows, nested jobs cannot exceed the caller's token permissions. 1. Runner labels match case-insensitively, and `runs-on` accepts an array from an expression. Runner PR: https://gitea.com/gitea/runner/pulls/1247 Docs PR: https://gitea.com/gitea/docs/pulls/553 Fixes: https://github.com/go-gitea/gitea/issues/38990 Fixes: https://github.com/go-gitea/gitea/issues/39382 Fixes: https://github.com/go-gitea/gitea/issues/32364 Fixes: https://github.com/go-gitea/gitea/issues/36077 Fixes: https://github.com/go-gitea/gitea/issues/23277 Fixes: https://github.com/go-gitea/gitea/issues/29020 Co-authored-by: Claude (Opus 5) <noreply@anthropic.com> Co-authored-by: Zettat123 <zettat123@gmail.com>	2026-09-25 00:06:42 +02:00
Zettat123	9fc5d20006	feat(actions): add force-cancel workflow run API (#38756) ... Add `POST /repos/{owner}/{repo}/actions/runs/{run}/force-cancel`, the counterpart of [GitHub's force-cancel endpoint](https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2026-03-10#force-cancel-a-workflow-run). It cancels a run like `POST .../cancel`, but bypasses the graceful cancelling handshake with the runner and stops running tasks immediately. Permissions and responses match the `/cancel` endpoint. References: - https://github.blog/changelog/2023-09-21-github-actions-force-cancel-workflows/ - https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2026-03-10#force-cancel-a-workflow-run - https://github.com/orgs/community/discussions/123240	2026-08-07 14:38:14 +00:00
3 people	c210ef6dbb	fix(actions): allow cancelling runs without running jobs (#35842) ... My idea is to allow cancelling an stuck run with all jobs done, in case such a bug happens again to not require admin commands. Related #35832 Co-authored-by: Zettat123 <zettat123@gmail.com> Co-authored-by: silverwind <me@silverwind.io>	2026-08-06 23:52:01 +00:00
6 people	a65f422b89	feat(actions): Add Actions API endpoints for workflow run management and logs (#35382) ... Implements the missing REST API endpoints for Actions workflow run management: 1. `POST /actions/runs/{run}/cancel` cancels a run and its jobs, `409` when it already finished 1. `POST /actions/runs/{run}/approve` approves a run awaiting approval, idempotent, `409` when it never awaited one 1. `GET /actions/runs/{run}/logs` downloads the latest attempt's job logs as a zip archive `ActionWorkflowRun` gains `created_at`, `updated_at` and the `jobs_url`, `logs_url`, `artifacts_url`, `cancel_url` and `rerun_url` fields, and now always emits `conclusion` and `head_branch`. Cancellation is shared with the web handler in `services/actions`. Fixes https://github.com/go-gitea/gitea/issues/35176 Fixes https://github.com/go-gitea/gitea/issues/36554 --------- Co-authored-by: Claude Sonnet 4.6 <claude-sonnet-4-6@anthropic.com> Co-authored-by: OpenCode Agent <opencode@rossgolder.com> Co-authored-by: Nicolas <bircni@icloud.com> Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2026-08-02 12:22:07 +08:00