[API] GetRelease by tag only return release #14397
No reviewers
Labels
No Label
backport/done
backport/v1.0
backport/v1.1
backport/v1.10
backport/v1.11
backport/v1.12
backport/v1.13
backport/v1.14
backport/v1.15
backport/v1.2
backport/v1.3
backport/v1.4
backport/v1.5
backport/v1.6
backport/v1.7
backport/v1.8
backport/v1.9
bounty
changelog
dependencies
frontport/done
frontport/main
good first issue
Hacktoberfest
hacktoberfest-accepted
in progress
kind/api
kind/breaking
kind/bug
kind/build
kind/deployment
kind/deprecated
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/misc
kind/moderation
kind/package
kind/proposal
kind/question
kind/refactor
kind/regression
kind/security
kind/summary
kind/testing
kind/translation
kind/ui
kind/upstream-related
kind/usability
kind/ux
lgtm/done
lgtm/need 1
lgtm/need 2
performance/bigrepo
performance/cpu
performance/memory
performance/speed
priority/critical
priority/low
priority/maybe
priority/medium
proposal/rejected
reviewed/confirmed
reviewed/duplicate
reviewed/fixed
reviewed/invalid
reviewed/not-a-bug
reviewed/wontfix
skip-changelog
stale
status/blocked
status/needs-feedback
status/wip
theme/2fa
theme/authentication
theme/avatar
theme/backup-restore
theme/docker
theme/federation
theme/issues
theme/kanban
theme/markdown
theme/migration
theme/mobile
theme/pr
theme/signing
theme/sqlite
theme/timetracker
theme/webhook
theme/wiki
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lunny/gitea#14397
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "pr-2edf7af9-56b4-48f6-ace2-decb1a5eaa3b"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
get release by tag should filter out tag releases to be consistent with list releases and get by id
There is a inconsistency between the 'list releases for repo' and 'get release by tag'.
The former filters out any release that is_tag=true where as the later includes them.
So there is no consistent way to identify if a release exists for a given tag name.
If I iterate the 'list releases for repo' results it wont be there. If I use 'get release by tag' it will be there but won't have any fields like title/notes/commitssh
@ -52,3 +51,4 @@
ctx.NotFound()
return
}
ctx.Error(http.StatusInternalServerError, "GetRelease", err)
I don't think it's needed to check repoid
@ -52,3 +51,4 @@
ctx.NotFound()
return
}
ctx.Error(http.StatusInternalServerError, "GetRelease", err)
Sure, i've removed that test
this is a breaking change!
and should at first be considdered carefully!
@ -52,3 +51,4 @@
ctx.NotFound()
return
}
ctx.Error(http.StatusInternalServerError, "GetRelease", err)
this is already checked!!! (at L48)
the only new thing is the
release.IsTag
check ... witch will break thingsIf we are going this way, we have to invent a new endpoint for git tags only