Beowulf commented

Owner

Please collect snippets and points of interest for the monthly report here.

Note: The we forge section needs to include the contributors from 31.01. too. See: #726 (comment)

Please collect snippets and points of interest for the monthly report here. _Note: The we forge section needs to include the contributors from 31.01. too. See: https://codeberg.org/forgejo/website/pulls/726#issuecomment-10265288_

Beowulf added the

Blog post

label

2026-01-30 18:24:14 +01:00

mfenniak commented

2026-02-24 17:11:55 +01:00

Member

Forgejo runner v12.7.0

Forgejo runner v12.7.0 was released on February 18th, bringing a major new multiple-connection feature that increases the flexibility of Forgejo runner deployments along with a handful of bug-fixes in podman container shutdown, chained reusable workflows, parsing of output variables, and log buffer flushing on host-based executors & LXC.

The new multiple connection capability can be used across multiple servers, such as receiving jobs from Codeberg and a private Forgejo instance. It can also be utilized to register a runner multiple times to the same Forgejo server, connecting to multiple different organizations, users, or repositories.

This capability has been built with a fully backward-compatible design. If you have no interest in using multiple connections, then no changes are required in the runner installation.

Multiple connections are the first feature to be delivered in a line of enhancements coming as contributors on the runner work to deprecate the .runner state file to simplify registration and management of Forgejo runner. As more enhancements are ongoing in this area, updated documentation showing multiple registrations hasn't yet been completed -- so here's a quick guide on how to use the new capability:

When runner is registered with a Forgejo server, it creates a .runner state file that contains some information about the server that the runner is connecting to:

{
  "WARNING": "This file is automatically generated by forgejo-runner. Do not edit it manually unless you know what you are doing. Removing this file will cause act runner to re-register as a new runner.",
  "id": 13,
  "uuid": "a605af85-59cd-4643-b519-5dd694c5789f",
  "name": "my-runner",
  "token": "c0524ac29795ed0ba433229d0e22b37b4ac713c0",
  "address": "https://example.com/",
  "labels": [
    "docker:docker://node:current-bookworm",
    "bare-metal:host"
  ]
}

The new multiple connection capability is enabled simply by moving this information into the runner's config file:

# other config data:
# log: ...
# runner: ...
# cache: ...
# container: ...
# host: ...

server:
  connections:
    forgejo1:
      url: https://example.com/
      uuid: a605af85-59cd-4643-b519-5dd694c5789f
      token: c0524ac29795ed0ba433229d0e22b37b4ac713c0
      labels:
        - docker:docker://node:current-bookworm
        - bare-metal:host

Remove the .runner file after server.connections is configured.
Ensure that the forgejo-runner daemon command is run with -c /path/to/config.yaml CLI option, as config files are optional and are not loaded from a default path.
To add more connections, either consolidate multiple existing .runner files from different installations into server.connections, or, use forgejo-runner register to create a new .runner file and then repeat step 2 and 3.

More detailed information on the options available are documented in the example config file, including: how to set different labels for each connection, and how to use an external file for the token secret value for enhanced security.

--

cc @aahlenst

# Forgejo runner v12.7.0 [Forgejo runner v12.7.0](https://code.forgejo.org/forgejo/runner/releases/tag/v12.7.0) was released on February 18th, bringing a major new multiple-connection feature that increases the flexibility of Forgejo runner deployments along with a handful of bug-fixes in podman container shutdown, chained reusable workflows, parsing of output variables, and log buffer flushing on host-based executors & LXC. The new multiple connection capability can be used across multiple servers, such as receiving jobs from Codeberg and a private Forgejo instance. It can also be utilized to register a runner multiple times to the same Forgejo server, connecting to multiple different organizations, users, or repositories. This capability has been built with a fully backward-compatible design. If you have no interest in using multiple connections, then no changes are required in the runner installation. Multiple connections are the first feature to be delivered in a line of enhancements coming as contributors on the runner work to [deprecate the `.runner` state file](https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues/88) to simplify registration and management of Forgejo runner. As more enhancements are ongoing in this area, updated documentation showing multiple registrations hasn't yet been completed -- so here's a quick guide on how to use the new capability: 1. When runner is registered with a Forgejo server, it creates a `.runner` state file that contains some information about the server that the runner is connecting to: ```json { "WARNING": "This file is automatically generated by forgejo-runner. Do not edit it manually unless you know what you are doing. Removing this file will cause act runner to re-register as a new runner.", "id": 13, "uuid": "a605af85-59cd-4643-b519-5dd694c5789f", "name": "my-runner", "token": "c0524ac29795ed0ba433229d0e22b37b4ac713c0", "address": "https://example.com/", "labels": [ "docker:docker://node:current-bookworm", "bare-metal:host" ] } ``` 2. The new multiple connection capability is enabled simply by moving this information into the runner's config file: ```yaml # other config data: # log: ... # runner: ... # cache: ... # container: ... # host: ... server: connections: forgejo1: url: https://example.com/ uuid: a605af85-59cd-4643-b519-5dd694c5789f token: c0524ac29795ed0ba433229d0e22b37b4ac713c0 labels: - docker:docker://node:current-bookworm - bare-metal:host ``` 3. Remove the `.runner` file after `server.connections` is configured. 4. Ensure that the `forgejo-runner daemon` command is run with `-c /path/to/config.yaml` CLI option, as config files are optional and are not loaded from a default path. 5. To add more connections, either consolidate multiple existing `.runner` files from different installations into `server.connections`, or, use `forgejo-runner register` to create a new `.runner` file and then repeat step 2 and 3. More detailed information on the options available are documented in the [example config file](https://code.forgejo.org/forgejo/runner/src/commit/9ff65b1a72811f90c4655cdf863aec92206aa774/internal/pkg/config/config.example.yaml#L220-L256), including: how to set different labels for each connection, and how to use an external file for the `token` secret value for enhanced security. -- cc @aahlenst

👍 1

mfenniak commented

2026-03-01 04:23:14 +01:00

Member

FOSDEM 2026

Forgejo contributors attended FOSDEM 2026 early in the month. Forgejo was involved in a few presentations:

Otto Richter gave a presentation on Understanding developer needs.
Jos van den Oever gave a presentation on Building a TODO app on top of Forgejo.
Akashdeep Dhar & Tomáš Hrčka gave a presentation on Forging Fedora Project’s Future With Forgejo.

Following in-person discussions at FOSDEM among some available contributors, a new proposal for changes to Forgejo's user research, design, and implementation workflow was published and discussed.

FOSDEM also enabled Forgejo contributors to start discussions on new funding opportunities with a large public institution, and the community is collecting input on which projects may be applicable for scaling up development efforts.

# FOSDEM 2026 Forgejo contributors attended FOSDEM 2026 early in the month. Forgejo was involved in a few presentations: - Otto Richter gave a presentation on [Understanding developer needs](https://fosdem.org/2026/schedule/event/EXQFAR-forgejo-developer-centric-user-needs-and-design/). - Jos van den Oever gave a presentation on [Building a TODO app on top of Forgejo](https://fosdem.org/2026/schedule/event/ZZNCKU-building_a_todo_app_on_top_of_forgejo/). - Akashdeep Dhar & Tomáš Hrčka gave a presentation on [Forging Fedora Project’s Future With Forgejo](https://fosdem.org/2026/schedule/event/A8XVNS-forging-fedora-projects-future-with-forgejo/). Following in-person discussions at FOSDEM among some available contributors, a new proposal for changes to Forgejo's user research, design, and implementation workflow was [published and discussed](https://codeberg.org/forgejo/discussions/issues/415#issuecomment-10312916). FOSDEM also enabled Forgejo contributors to start discussions on new funding opportunities with a large public institution, and [the community is collecting input on which projects](https://codeberg.org/forgejo/sustainability/issues/163) may be applicable for scaling up development efforts.

mfenniak commented

2026-03-01 04:31:41 +01:00

Member

Notable Discussions

Public institution is interested in Forgejo; what do you want to see supported?
Codeberg e.V. has proposed a community agreement to speak on behalf of the community in future funding discussions
Ongoing proposals to improve Forgejo's user research, design, and implementation workflow
Who can use the name "Forgejo" in domains and marketing?
Feature proposal to add a pull-through cache capability to Forgejo
Would publishing Forgejo Runner for macOS and Windows be compatible with Forgejo's values?
Improvements to Forgejo's integration testing have moved from a proposal through proof-of-concept stages and received community feedback
Feature proposal to add an "Environments" capability to Forgejo Actions, and subsequent design iterations
Proposal to change CONTRIBUTING.md to have practical steps to get started
An older thread on Native Kubernetes-based Forgejo Runners has been revived with new concepts and design discussion

# Notable Discussions - [Public institution is interested in Forgejo; what do you want to see supported?](https://codeberg.org/forgejo/sustainability/issues/163) - Codeberg e.V. has [proposed a community agreement](https://codeberg.org/forgejo/discussions/issues/446) to speak on behalf of the community in future funding discussions - [Ongoing proposals to improve Forgejo's user research, design, and implementation workflow](https://codeberg.org/forgejo/discussions/issues/415#issuecomment-10312916) - [Who can use the name "Forgejo" in domains and marketing?](https://codeberg.org/forgejo/discussions/issues/434) - [Feature proposal to add a pull-through cache capability to Forgejo](https://codeberg.org/forgejo/discussions/issues/444) - [Would publishing Forgejo Runner for macOS and Windows be compatible with Forgejo's values?](https://codeberg.org/forgejo/discussions/issues/447) - [Improvements to Forgejo's integration testing have moved from a proposal through proof-of-concept stages and received community feedback](https://codeberg.org/forgejo/discussions/issues/170#issue-769664) - [Feature proposal to add an "Environments" capability to Forgejo Actions, and subsequent design iterations](https://codeberg.org/forgejo/discussions/issues/440) - [Proposal to change CONTRIBUTING.md to have practical steps to get started](https://codeberg.org/forgejo/discussions/issues/449) - An older thread on [Native Kubernetes-based Forgejo Runners](https://codeberg.org/forgejo/discussions/issues/66) has been revived with new concepts and design discussion

mahlzahn commented

2026-03-01 07:54:05 +01:00

Member

Contributing

A new make command was introduced to ensure that the same go backend checks are performed locally on the developer's computer and in the Forgejo's CI runs. Contributors are asked to run make pr-go before submitting a pull request. @slink

# Contributing A new [`make` command was introduced](https://codeberg.org/forgejo/forgejo/pulls/11053) to ensure that the same go backend checks are performed locally on the developer's computer and in the Forgejo's CI runs. Contributors are asked to run `make pr-go` before submitting a pull request. @slink

viceice commented

2026-03-01 08:27:59 +01:00

Owner

Helm chart

Helm chart had two minor releases related to kubernetes TCP route.

https://code.forgejo.org/forgejo-helm/forgejo-helm/releases

# Helm chart Helm chart had two minor releases related to kubernetes TCP route. - https://code.forgejo.org/forgejo-helm/forgejo-helm/releases

viceice commented

2026-03-01 08:36:11 +01:00

Owner

Infrastructure

network incident on Hetzner caused a short outage
Renovate workload where converted to use renovate-operator so it allows on demand jobs via checkboxes on PR or dashboard issue
Forgejo code got OpenSearch for issue and code indexing

# Infrastructure - network incident on Hetzner caused a short outage - Renovate workload where converted to use renovate-operator so it allows on demand jobs via checkboxes on PR or dashboard issue - Forgejo code got OpenSearch for issue and code indexing

~~Beowulf referenced this issue 2026-03-08 18:41:48 +01:00~~

Forgejo monthly report - February 2026 #790

Rows
Columns

Monthly report for February 2026 #730

Forgejo runner v12.7.0

FOSDEM 2026

Notable Discussions

Contributing

Helm chart

Infrastructure