When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with "cancel-in-progress" enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.