V1.22 #32651
Closed
V1.22 #32651
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o-gitea#30979) Backport go-gitea#30977 by @lunny The double quotes and the prefix/suffix space are unnecessary. Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
…ase (go-gitea#30984) (go-gitea#30986) We should call `notify_service.NewRelease` when a release is created from an existing tag. Co-authored-by: Zettat123 <[email protected]>
Backport go-gitea#30966 by silverwind Co-authored-by: silverwind <[email protected]>
Just a small commit to fix a wrong label for id. Thanks and cheers! Signed-off-by: Frank Villaro-Dixon <[email protected]> Co-authored-by: Frank Villaro-Dixon <[email protected]>
Backport go-gitea#30996 by @silverwind Result of `make update-py` Fixes: https://github.com/go-gitea/gitea/security/dependabot/65 Co-authored-by: silverwind <[email protected]>
…tea#31001) Backport go-gitea#30990 by @wxiaoguang Regression of Fix issue/PR title edit (go-gitea#30858) Co-authored-by: wxiaoguang <[email protected]>
Backport go-gitea#30963 by wxiaoguang Fix go-gitea#30921 Co-authored-by: wxiaoguang <[email protected]>
…ior (go-gitea#31003) (go-gitea#31020) Backport go-gitea#31003 by wxiaoguang Fix go-gitea#31002 1. Mention Make sure `Host` and `X-Fowarded-Proto` headers are correctly passed to Gitea 2. Clarify the basic requirements and move the "general configuration" to the top 3. Add a comment for the "container registry" 4. Use 1.21 behavior if the reverse proxy is not correctly configured Co-authored-by: wxiaoguang <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
Backport go-gitea#31012 by wxiaoguang Co-authored-by: wxiaoguang <[email protected]>
Backport go-gitea#31008 by @lunny Extract from go-gitea#30995 Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: silverwind <[email protected]>
Backport go-gitea#30999 by wxiaoguang Fix go-gitea#30992 Co-authored-by: wxiaoguang <[email protected]>
Backport go-gitea#31011 by wxiaoguang Co-authored-by: wxiaoguang <[email protected]>
…itea#31014) (go-gitea#31027) Backport go-gitea#31014 by wxiaoguang Co-authored-by: wxiaoguang <[email protected]>
… (go-gitea#31026) Backport go-gitea#31013 by wxiaoguang Co-authored-by: wxiaoguang <[email protected]>
…ea#30974) (go-gitea#31029) Backport go-gitea#30974 by Zettat123 Co-authored-by: Zettat123 <[email protected]> Co-authored-by: KN4CK3R <[email protected]>
Backport go-gitea#31023 by wxiaoguang Co-authored-by: wxiaoguang <[email protected]>
…31028) (go-gitea#31032) Backport go-gitea#31028 by @kemzeb From go-gitea#31018 (comment). This commit removes the link to a deleted branch name because it returns a 404 while it is in this deleted state. GitHub also throws a 404 when navigating to a branch link that was just deleted, but this deleted branch is removed from the branch list after a page refresh. Since with Gitea this deleted branch would be kept around for quite some time (well, until the "cleanup deleted branches" cron job begins), it makes sense to not have this as a link that users can navigate to. Co-authored-by: Kemal Zebari <[email protected]>
…#31042) Backport go-gitea#31015 by @denyskon Do not try to create a new authorization grant when one exists already, thus preventing a DB-related authorization issue. Fix go-gitea#30790 (comment) Co-authored-by: Denys Konovalov <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
…ered (go-gitea#30780) (go-gitea#31039) Backport go-gitea#30780 by @lunny Replace go-gitea#25741 Close go-gitea#24445 Close go-gitea#30658 Close go-gitea#20646 ~Depends on go-gitea#30805~ Since go-gitea#25741 has been rewritten totally, to make the contribution easier, I will continue the work in this PR. Thanks @6543 Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: 6543 <[email protected]> Co-authored-by: wxiaoguang <[email protected]>
go-gitea#31022) (go-gitea#31049) Backport go-gitea#31022 by @kemzeb Syncs up docs associated to actions and deleted branch cleanup i.e. in custom/app.example.ini and the config cheat sheet. Co-authored-by: Kemal Zebari <[email protected]>
…ea#31048) Backport go-gitea#31034 by @lunny Fix go-gitea#25897 (comment) Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: silverwind <[email protected]> Co-authored-by: yp05327 <[email protected]>
…o-gitea#31043) Backport go-gitea#25812 ~~ps: removed some new codes in `tests/integration/pull_merge_test.go`~~ --------- Co-authored-by: silverwind <[email protected]> Co-authored-by: Lunny Xiao <[email protected]> Co-authored-by: wxiaoguang <[email protected]>
Backport go-gitea#31047 by @techknowlogick Co-authored-by: techknowlogick <[email protected]>
…n field (go-gitea#31045) (go-gitea#31059) Backport go-gitea#31045 by @Zettat123 Fix go-gitea#31044 According to [GitHub issue template documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#attributes-for-dropdown), the `default` attribute can be used to specify the preselected option for a dropdown field. Co-authored-by: Zettat123 <[email protected]>
…#31081) Backport go-gitea#28435 by Chief-Detektor Co-authored-by: André Rosenhammer <[email protected]>
…ea#31098) Backport go-gitea#31092 by @lunny Fix go-gitea#31087 Co-authored-by: Lunny Xiao <[email protected]>
…a#31097) Backport go-gitea#31089 by @silverwind Presumably a regression from go-gitea#30325, these menus were showing a border radius on hover, which is fixed with this change. <img width="154" alt="image" src="https://github.com/go-gitea/gitea/assets/115237/eafdc1c5-3cf5-48d1-86c4-21c58f92cfaf"> Co-authored-by: silverwind <[email protected]>
…gitea#32539) (go-gitea#32549) backport go-gitea#32539 --------- Co-authored-by: wxiaoguang <[email protected]>
…#32243) (go-gitea#32550) Backport go-gitea#32243 by @lunny Partially fix go-gitea#31345 Co-authored-by: Lunny Xiao <[email protected]>
…go-gitea#32528) (go-gitea#32547) Backport go-gitea#32528 - Move models/GetForks to services/FindForks - Add doer as a parameter of FindForks to check permissions - Slight performance optimization for get forks API with batch loading of repository units - Add tests for forking repository to organizations --------- Co-authored-by: wxiaoguang <[email protected]>
Backport go-gitea#32560 by @lunny PushMirrors only be used in the repository setting page. So it should not be loaded on every repository page. Co-authored-by: Lunny Xiao <[email protected]>
A quick fix for go-gitea#32568 Partially backport from go-gitea#32571
…o-gitea#32580) Backport go-gitea#32527 We have some actions that leverage the Gitea API that began receiving 401 errors, with a message that the user was not found. These actions use the `ACTIONS_RUNTIME_TOKEN` env var in the actions job to authenticate with the Gitea API. The format of this env var in actions jobs changed with go-gitea/pull/28885 to be a JWT (with a corresponding update to `act_runner`) Since it was a JWT, the OAuth parsing logic attempted to parse it as an OAuth token, and would return user not found, instead of falling back to look up the running task and assigning it to the actions user. Make ACTIONS_RUNTIME_TOKEN in action runners could be used, attempting to parse Oauth JWTs. The code to parse potential old `ACTION_RUNTIME_TOKEN` was kept in case someone is running an older version of act_runner that doesn't support the Actions JWT.
Backport go-gitea#32540 by @lunny Fix go-gitea#31480 Co-authored-by: Lunny Xiao <[email protected]>
Partially backport go-gitea#32351
… (go-gitea#32592) Backport go-gitea#32313 go-gitea#29248 didn't modify the view page. The class name is not good enough, so this is a quick fix. Before: org:  user:  After: org:  user: (no change)  Co-authored-by: yp05327 <[email protected]>
Resolves go-gitea#20475 Backport go-gitea#31863 Co-authored-by: Job <[email protected]>
Backport go-gitea#32360 Try to fix go-gitea#31792 Credit to @jeroenlaylo Copied from go-gitea#31792 (comment) Co-authored-by: wxiaoguang <[email protected]>
This PR rewrites `GetReviewer` function and move it to service layer. Reviewers should not be watchers, so that this PR removed all watchers from reviewers. When the repository is under an organization, the pull request unit read permission will be checked to resolve the bug of Fix go-gitea#32394 Backport go-gitea#32415
Add release note for v1.22.4 --------- Co-authored-by: Kyle D. <[email protected]>
GiteaBot
added
the
lgtm/need 2
Collaborator
|
@fumao I noticed you've updated the locales for non-English languages. These will be overwritten during the sync from our translation tool Crowdin. If you'd like to contribute your translations, please visit https://crowdin.com/project/gitea. Please revert the changes done on these files. 🍵 |
github-actions
bot
added
modifies/translation
modifies/api
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
18 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check the following:
mainbranch, pull requests on release branches are only allowed for backports.---.