forgejo-backport-action 7b4ea980b2 [v11.0/forgejo] fix: make /repos/search?uid=-2 return zero results, no repos with that owner (#12148) ... **Backport:** https://codeberg.org/forgejo/forgejo/pulls/12144 API calls to `.../api/v1/repos/search?uid=-2&archived=false` currently do not apply the filter `uid` because of the negative value. This can occur when APIs are interacting with `${{ forgejo.token }}` and believe they're operating as the Forgejo Actions user, which has UID -2. In combination with the security checks that occur in the `/repos/search` API to validate that repositories accessed are visible to the user, this can result in 500 error responses when a more correct expectation would be to receive no repositories: da8898822c/routers/api/v1/repo/repo.go (L237-L242) ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). 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 for Go changes - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### 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 - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12148 Reviewed-by: Gusted <gusted@noreply.codeberg.org> Co-authored-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org> Co-committed-by: forgejo-backport-action <forgejo-backport-action@noreply.codeberg.org>		2026-04-16 21:01:00 +02:00
..
e2e	[v11.0/forgejo] chore(e2e): test flakiness in webauthn.test.e2e.ts (#9662) (#9673)	2025-10-13 20:47:38 +02:00
fuzz	[v11.0/forgejo] chore: branding import path (#7354)	2025-03-27 20:13:05 +00:00
gitea-lfs-meta	Test views of LFS files (#22196)	2022-12-23 07:41:56 +08:00
gitea-repositories-meta	[v11.0/forgejo] chore: branding import path (#7354)	2025-03-27 20:13:05 +00:00
integration	[v11.0/forgejo] fix: make /repos/search?uid=-2 return zero results, no repos with that owner (#12148)	2026-04-16 21:01:00 +02:00
testdata/data	Add artifacts test fixture (#30300)	2024-11-05 09:33:15 +01:00
mysql.ini.tmpl	chore: improve slow tests	2024-11-14 12:41:11 +01:00
pgsql.ini.tmpl	chore: improve slow tests	2024-11-14 12:41:11 +01:00
sqlite.ini.tmpl	test: use memory for integration and journal for migration	2024-11-14 15:38:06 +01:00
test_utils.go	[v11.0/forgejo] 2025-11-21 combined security patches (#10039)	2025-11-21 04:31:31 +01:00