Latest commits for branch codeberg-12

cb/feat: add symbol of tolerance (!114)

Gusted — Sat, 11 Oct 2025 21:26:17 +0200

cb/feat: add symbol of tolerance (!114) Ref: !109 Add a symbol of tolerance via the queer flag in the footer. Always show it for guests, otherwise show it for `/`, `/user`, `/about`, `/explore` and all Codeberg organizations related pages. Reviewed-on: https://codeberg.org/Codeberg-Infrastructure/forgejo/pulls/114 Reviewed-by: Otto Co-authored-by: Gusted Co-committed-by: Gusted

Update to latest Forgejo v12

Gusted — Tue, 07 Oct 2025 22:32:05 +0200

Update to latest Forgejo v12

[v12.0/forgejo] fix: allow unactivated users to send recovery mails (#9514)

forgejo-backport-action — Fri, 03 Oct 2025 08:07:24 +0200

[v12.0/forgejo] fix: allow unactivated users to send recovery mails (#9514) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/9504 With forgejo/forgejo#9075 the `GetUserByEmail` now actually only used activated emails. This however broke sending recovery mails to unactivated users, as their email are not yet activated. Use the newly introduced function `GetUserByEmailSimple` to not care about this activated email requirement and also avoid the no-reply address being a valid email address for this functionality. Co-authored-by: Gusted Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9514 Reviewed-by: Gusted Co-authored-by: forgejo-backport-action Co-committed-by: forgejo-backport-action

Update to latest Forgejo v12

Codeberg Build Maintainers — Wed, 01 Oct 2025 19:05:28 +0000

Update to latest Forgejo v12

[v12.0/forgejo] fix: package cleaned rule fails if the keep count is too high (#9470)

forgejo-backport-action — Mon, 29 Sep 2025 18:00:43 +0200

[v12.0/forgejo] fix: package cleaned rule fails if the keep count is too high (#9470) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/9468 If the keep count of a cleanup rule is greater than the number of available packages, it fails with: ``` panic(boundsError{x: int64(x), signed: true, y: y, code: boundsSliceB}) .../packages/packages.go:175 .../routers/web/org/setting_packages.go:108 ``` Regression of https://codeberg.org/forgejo/forgejo/pulls/9219/files Refs https://codeberg.org/forgejo/forgejo/issues/9461 ## Release notes - Bug fixes - [PR](https://codeberg.org/forgejo/forgejo/pulls/9468): package cleaned rule fails if the keep count is too high Co-authored-by: Earl Warren Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9470 Reviewed-by: Earl Warren Co-authored-by: forgejo-backport-action Co-committed-by: forgejo-backport-action

[v12.0/forgejo] fix: upgrade to the ldap version used for testing to 2.5 (#9419)

forgejo-backport-action — Thu, 25 Sep 2025 14:57:03 +0200

[v12.0/forgejo] fix: upgrade to the ldap version used for testing to 2.5 (#9419) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/9417 The LDAP server ontainer image used for tests is pre-populated with: - https://github.com/rroemhild/docker-test-openldap/tree/v2.5.0/rootfs/ - https://code.forgejo.org/forgejo/forgejo-test-openldap/src/branch/main/rootfs (adds files) --- use https://code.forgejo.org/forgejo/forgejo-test-openldap with ldap 2.5 instead of a stretch based image with ldap 2.4 that cannot be rebuilt. - user sshuser exists specifically to test sshKey sync instead of a modified hermes user - user bender was different from the base image for no useful purpose (accent in the name), remove the accent - the port is 10389 by default instead of 389 Refs https://codeberg.org/forgejo/forgejo/issues/9406 Co-authored-by: Earl Warren Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9419 Reviewed-by: Earl Warren Co-authored-by: forgejo-backport-action Co-committed-by: forgejo-backport-action

[v12.0/forgejo] fix: use correct commit when fetching patch view for review comments (#9374)

forgejo-backport-action — Mon, 22 Sep 2025 03:28:05 +0200

[v12.0/forgejo] fix: use correct commit when fetching patch view for review comments (#9374) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/9264 This is effectively a clean revert of e7a77d32cc, which for some reason broke this logic. Yes, always having the latest code shown in the diff is nice, but doing this mismatches the commitID and the line number the comment is being posted on, which very easily and frequently leads to reviews that show a completely nonsensical patch above them, cause the code it's referring too shifted by several lines since the time the review was started and the time it was posted. Co-authored-by: BtbN Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9374 Reviewed-by: Gusted Co-authored-by: forgejo-backport-action Co-committed-by: forgejo-backport-action

Update to latest Forgejo v12

Gusted — Sat, 20 Sep 2025 17:27:24 +0200

Update to latest Forgejo v12

CB/tmpl: update number of ev members

Codeberg Build Maintainers — Sat, 20 Sep 2025 14:11:29 +0000

CB/tmpl: update number of ev members

[v12.0/forgejo] fix: do not display the title of unsubscribed issues or pull requests in the notification web page (#9364)

forgejo-backport-action — Fri, 19 Sep 2025 23:12:57 +0200

[v12.0/forgejo] fix: do not display the title of unsubscribed issues or pull requests in the notification web page (#9364) **Backport:** https://codeberg.org/forgejo/forgejo/pulls/9362 Do not display the title of unsubscribed issues or pull requests in the notification web page . The title of some random issues or pull requests from repositories were accidentally displayed in the notifications of a user. It was a rare occurrence, caused by an incorrect comparison of two unrelated unique identifiers that are unlikely to match (the id of the notification and the id of a repository). If the issue or the pull request belonged to a private repository to which the user had no read access, only the title was leaked. The user was denied permission to view the issue or the pull request when clicking on the link displayed in the notifications web page. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests - I added test coverage for Go changes... - [x] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [x] I did not document these changes and I do not expect someone else to do it. ### Release notes - [ ] I do not want this change to show in the release notes. - [ ] I want the title to show in the release notes with a link to this pull request. - [x] I want the content of the `release-notes/.md` to be be used for the release notes instead of the title. ## Release notes - Security bug fixes - [PR](https://codeberg.org/forgejo/forgejo/pulls/9362): Do not display the title of unsubscribed issues or pull requests in the notification web page . The title of some random issues or pull requests from repositories were accidentally displayed in the notifications of a user. It was a rare occurrence, caused by an incorrect comparison of two unrelated unique identifiers that are unlikely to match (the id of the notification and the id of a repository). If the issue or the pull request belonged to a private repository to which the user had no read access, only the title was leaked. The user was denied permission to view the issue or the pull request when clicking on the link displayed in the notifications web page. Co-authored-by: Earl Warren Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9364 Reviewed-by: Earl Warren Co-authored-by: forgejo-backport-action Co-committed-by: forgejo-backport-action