Latest commits for branch codeberg-14

CB/bp: fix: allow Actions runner to recover tasks lost during fetching from intermittent errors (#11401)

Mathieu Fenniak — Fri, 27 Feb 2026 03:00:04 +0100

CB/bp: fix: allow Actions runner to recover tasks lost during fetching from intermittent errors (#11401) Probably fixes (or improves, at least) https://code.forgejo.org/forgejo/runner/issues/1391, paired with the runner implementation https://code.forgejo.org/forgejo/runner/pulls/1393. When the FetchTask() API is invoked to create a task, unpreventable environmental errors may occur; for example, network disconnects and timeouts. It's possible that these errors occur after the server-side has assigned a task to the runner during the API call, in which case the error would cause that task to be lost between the two systems -- the server will think it's assigned to the runner, and the runner never received it. This can cause jobs to appear stuck at "Set up job". The solution implemented here is idempotency in the FetchTask() API call, which means that the "same" FetchTask() API call is expected to return the same values. Specifically, the runner creates a unique identifier which is transmitted to the server as a header `x-runner-request-key` with each FetchTask() invocation which defines the sameness of the call, and the runner retains the value until the API call receives a successful response. The server implementation returns the same tasks back if a second (or Nth) call is received with the same `x-runner-request-key` header. In order to accomplish this is records the `x-runner-request-key` value that is used with each request that assigns tasks. As a complication, the Forgejo server is unable to return the same `${{ secrets.forgejo_token }}` for the task because the server stores that value in a one-way hash in the database. To resolve this, the server regenerates the token when retrieving tasks for a second time. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11401 Reviewed-by: Andreas Ahlenstorf Co-authored-by: Mathieu Fenniak Co-committed-by: Mathieu Fenniak (cherry picked from commit 0ae62353862472ebd6bb2bdb44a8cc8354e89c27)

CB/fix: patch out retry button

Gusted — Fri, 27 Feb 2026 02:46:02 +0100

CB/fix: patch out retry button This feature never should have landed in Gitea, it's utterly broken because it only works where migration failed before any data was migrated. Which for Codeberg's use case is almost never the case and leads to retrying a migration that's bound to fail. This forces people to delete repository and fill out migration details, this is inconvenient but it's arguably more inconvenient seeing that retry button does not work.

CB/fix: continue on error for avatar strip exif

Gusted — Wed, 25 Feb 2026 01:34:59 +0100

CB/fix: continue on error for avatar strip exif https://codeberg.org/superseriousbusiness/exif-terminator/issues/16 Avatars might get changed, deleted during this doctor run.

CB/fix(footer): use
for blog link (!126)

0ko — Wed, 25 Feb 2026 01:03:24 +0100

CB/fix(footer): use

for blog link (!126) Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/126 Reviewed-by: Gusted Co-authored-by: 0ko <0ko@noreply.codeberg.org> Co-committed-by: 0ko <0ko@noreply.codeberg.org>

CB/fix: reduce deadlocks for commenting

Gusted — Wed, 25 Feb 2026 01:03:24 +0100

CB/fix: reduce deadlocks for commenting This is a try to avoid a long-running UPDATE query and instead opt it to be a long-running SELECT query that collects potential IDs and then have a fast UPDATE query. It is possible it will still lead to deadlocks, but we'll see. Most recent deadlocks was with commenting on issues (updating the num of comments count of the issue)

CB/ui: Update link color in homepage about box (!125)

Martijn Verkleij — Wed, 25 Feb 2026 01:03:24 +0100

CB/ui: Update link color in homepage about box (!125) Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/125 Reviewed-by: Gusted Co-authored-by: Martijn Verkleij Co-committed-by: Martijn Verkleij

CB/meta: Improve custom theme explanation in README (!123)

Panagiotis "Ivory" Vasilopoulos — Wed, 25 Feb 2026 01:03:24 +0100

CB/meta: Improve custom theme explanation in README (!123) Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/123 Co-authored-by: Panagiotis "Ivory" Vasilopoulos Co-committed-by: Panagiotis "Ivory" Vasilopoulos

CB/ui: Make 'Forgejo' on homepage link to forgejo.org (!124)

Panagiotis "Ivory" Vasilopoulos — Wed, 25 Feb 2026 01:03:24 +0100

CB/ui: Make 'Forgejo' on homepage link to forgejo.org (!124) - Consistent with link in footer - Forgejo's homepage says that it's under the Codeberg e. V. umbrella - People that don't know what Forgejo is might not want to get the source code directly This change was made based on feedback I received on the homepage. Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/124 Co-authored-by: Panagiotis "Ivory" Vasilopoulos Co-committed-by: Panagiotis "Ivory" Vasilopoulos

CB/tmpl: update funding URL on the homepage

Hugo Peixoto — Wed, 25 Feb 2026 01:03:24 +0100

CB/tmpl: update funding URL on the homepage

CB/tmpl: Point to our documentation about licenses (!122)

Robert Wolff — Wed, 25 Feb 2026 01:03:24 +0100

CB/tmpl: Point to our documentation about licenses (!122) cherry-picked from 1509e29d94b4a6a8696879d1a5f6f0f7c7b24e5a Related: Codeberg/Community#1214 Co-authored-by: Otto Richter Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/122 Reviewed-by: Gusted Co-authored-by: Robert Wolff Co-committed-by: Robert Wolff