-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/api/v1/orgs has become an authenticated endpoint with 0.19 #24159
Comments
@wxiaoguang If it should be public, then |
2 tasks
techknowlogick
pushed a commit
that referenced
this issue
Apr 21, 2023
- [x] Identify endpoints that should be public - [x] Update integration tests Fix #24159
2 tasks
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Apr 21, 2023
- [x] Identify endpoints that should be public - [x] Update integration tests Fix go-gitea#24159
silverwind
pushed a commit
that referenced
this issue
Apr 21, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
We have CI for https://opendev.org where we are testing our upgrade of 1.18.5 to 1.19.1 [1].
We found that one of our CI tasks that gets the orgs from
api/v1/orgs
started failing returning a401
.I believe this is related to de484e8
It's not too hard to replicate this; as opendev.org is still on 1.18
The first returns json, the second not :) I'm not sure if this is intentional; it does seem like the public org listing probably doens't need to be an authenticated call?
[1] https://review.opendev.org/c/opendev/system-config/+/877541
Gitea Version
1.19.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Our gitea is built from upstream into a container
Database
None
The text was updated successfully, but these errors were encountered: