Do not use lower tag names to find releases/tags #29261
Merged
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
wolfogre
added
type/bug
backport/v1.21
GiteaBot
added
the
lgtm/need 2
lunny
approved these changes
Feb 19, 2024
GiteaBot
added
lgtm/need 1
Zettat123
approved these changes
Feb 19, 2024
GiteaBot
added
lgtm/done
lunny
added
the
reviewed/wait-merge
|
I was unable to create a backport for 1.21. @wolfogre, please send one manually. 🍵 |
GiteaBot
added
backport/manual
lunny
pushed a commit
that referenced
this pull request
Feb 19, 2024
Backport #29261. Fix #26090, see #26090 (comment) Since `TagName` stores the original tag name and `LowerTagName` stores the lower tag name, it doesn't make sense to use lowercase tags as `TagNames` in `FindReleasesOptions`. https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/services/repository/push.go#L396-L397 While the only other usage looks correct: https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/routers/web/repo/repo.go#L416
silverwind
pushed a commit
to silverwind/gitea
that referenced
this pull request
Feb 20, 2024
Fix go-gitea#26090, see go-gitea#26090 (comment) Since `TagName` stores the original tag name and `LowerTagName` stores the lower tag name, it doesn't make sense to use lowercase tags as `TagNames` in `FindReleasesOptions`. https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/services/repository/push.go#L396-L397 While the only other usage looks correct: https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/routers/web/repo/repo.go#L416
6543
pushed a commit
to 6543-forks/gitea
that referenced
this pull request
Feb 26, 2024
Fix go-gitea#26090, see go-gitea#26090 (comment) Since `TagName` stores the original tag name and `LowerTagName` stores the lower tag name, it doesn't make sense to use lowercase tags as `TagNames` in `FindReleasesOptions`. https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/services/repository/push.go#L396-L397 While the only other usage looks correct: https://github.com/go-gitea/gitea/blob/5e72526da4e915791f03af056890e16821bde052/routers/web/repo/repo.go#L416 (cherry picked from commit 0ea8de2)
|
Automatically locked because of our CONTRIBUTING guidelines |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix #26090, see #26090 (comment)
Since
TagNamestores the original tag name andLowerTagNamestores the lower tag name, it doesn't make sense to use lowercase tags asTagNamesinFindReleasesOptions.gitea/services/repository/push.go
Lines 396 to 397 in 5e72526
While the only other usage looks correct:
gitea/routers/web/repo/repo.go
Line 416 in 5e72526