--- title: Forgejo Runner v13.1.0 is available | daily.dev description: Forgejo Runner v13.1.0, released August 31, 2026, introduces an experimental plugin execution engine that lets developers create custom execution backends... canonical: https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Forgejo Runner v13.1.0 is available | daily.dev og:description: Forgejo Runner v13.1.0, released August 31, 2026, introduces an experimental plugin execution engine that lets developers create custom execution backends... og:url: https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk og:image: https://api.daily.dev/og/posts/znsVySHbK.png og:image:alt: Forgejo Runner v13.1.0 is available og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Forgejo Runner v13.1.0 is available **[Forgejo News](https://daily.dev/sources/forgejo)** · 7 min read · 23 upvotes · 2 comments ## Summary Forgejo Runner v13.1.0, released August 31, 2026, introduces an experimental plugin execution engine that lets developers create custom execution backends (like Firecracker microVMs, Kubernetes pods, or QEMU) as external gRPC-based applications rather than requiring the core team to build and maintain each engine. The plugin protocol is alpha and subject to change. The release also removes pseudo-tty terminal attachment from job command execution, a breaking change that can affect commands like `docker run -it` which now fail unless the `-t` flag is removed; this was an unanticipated side effect reported after release. The release also includes routine dependency upgrades and prep work for an upcoming Forgejo bug-fix. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does docker run -it fail in Forgejo Runner after upgrading to v13.1.0? Forgejo Runner v13.1.0 removed the pseudo-tty (pty) attachment previously applied to job command stdout and stderr. Commands like docker run -it that require a terminal will now fail because no terminal is attached. The fix is to remove the -t option from the command, since running docker run -i (without -t) works without a terminal attached. _Track breaking changes like this pty removal in Forgejo Runner releases on daily.dev before they hit your pipelines._ ### How does the new Forgejo Runner plugin execution engine work? Forgejo Runner v13.1.0 adds an experimental plugin execution engine that connects to an external daemon over gRPC, implementing the plugin.v1alpha service plus the standard grpc.health.v1 health check service. The runner calls RPCs like Capabilities, Create, Start, CopyIn, Exec, CopyOut, and Remove to run each job step, letting developers build custom execution backends such as Firecracker, Kubernetes pods, or systemd-nspawn containers without core team support. _Developers evaluating custom CI execution backends can follow how Forgejo's plugin protocol evolves on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@agustinbarrientos** · 0 upvotes > Will each job log the plugin version and environment image? `CopyIn` moves an entire action codebase into an external executor, so reproducibility could get messy fast. ## Similar posts on daily.dev - [Forgejo Runner v13.0.0 is available](https://daily.dev/posts/forgejo-runner-v13-0-0-is-available-i0a6tbihu) · Forgejo News · 7 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#cicd](https://daily.dev/tags/cicd), [#self-hosting](https://daily.dev/tags/self-hosting), [#grpc](https://daily.dev/tags/grpc), [#forgejo](https://daily.dev/tags/forgejo) [View this post on daily.dev](https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Forgejo Runner v13.1.0 is available","url":"https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk"},"datePublished":"2026-09-03T13:52:13.583Z","dateModified":"2026-09-03T14:11:14.003Z","description":"Forgejo Runner v13.1.0, released August 31, 2026, introduces an experimental plugin execution engine that lets developers create custom execution backends...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ecd9058ec824271361a436684af5bb15?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ecd9058ec824271361a436684af5bb15?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Forgejo News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Forgejo News","logo":"https://media.daily.dev/image/upload/s--Cq9uBvkb--/f_auto,q_auto/v1785052096/logos/forgejo?_a=BAMAMicg0","url":"https://daily.dev/sources/forgejo"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":23},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"open-source,cicd,self-hosting,grpc,forgejo","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Forgejo News","item":"https://daily.dev/sources/forgejo"},{"@type":"ListItem","position":3,"name":"Forgejo Runner v13.1.0 is available"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk","comment":[{"@type":"Comment","text":"Will each job log the plugin version and environment image? CopyIn moves an entire action codebase into an external executor, so reproducibility could get messy fast.","datePublished":"2026-09-08T01:36:35.186Z","url":"https://daily.dev/posts/znsVySHbK#c-mA3VRb3nN","author":{"@type":"Person","name":"Agustin Barrientos","url":"https://daily.dev/agustinbarrientos","image":"https://media.daily.dev/image/upload/s--5ayxQnqn--/f_auto/v1788281802/avatars/avatar_wQYYVe5Tbj0NJ7C7qPoa8?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/forgejo-runner-v13-1-0-is-available-znsvyshbk#faq","mainEntity":[{"@type":"Question","name":"Why does docker run -it fail in Forgejo Runner after upgrading to v13.1.0?","acceptedAnswer":{"@type":"Answer","text":"Forgejo Runner v13.1.0 removed the pseudo-tty (pty) attachment previously applied to job command stdout and stderr. Commands like docker run -it that require a terminal will now fail because no terminal is attached. The fix is to remove the -t option from the command, since running docker run -i (without -t) works without a terminal attached. Track breaking changes like this pty removal in Forgejo Runner releases on daily.dev before they hit your pipelines."}},{"@type":"Question","name":"How does the new Forgejo Runner plugin execution engine work?","acceptedAnswer":{"@type":"Answer","text":"Forgejo Runner v13.1.0 adds an experimental plugin execution engine that connects to an external daemon over gRPC, implementing the plugin.v1alpha service plus the standard grpc.health.v1 health check service. The runner calls RPCs like Capabilities, Create, Start, CopyIn, Exec, CopyOut, and Remove to run each job step, letting developers build custom execution backends such as Firecracker, Kubernetes pods, or systemd-nspawn containers without core team support. Developers evaluating custom CI execution backends can follow how Forgejo's plugin protocol evolves on daily.dev."}}]} ```