Drop deprecations #503
No reviewers
Labels
No Label
has/backport
has/pull
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#503
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "6543/go-sdk:start-0.15.0-dev"
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?
start v0.15.0 development
For a better changelog, maybe rename the PR to
drop deprecations & gitea <1.12.3 support
?Start v0.15.0 Developmentto Drop deprecations & gitea <1.12.3 supportI think it's too early to drop support for gitea 1.11 we want to make it possible for people to use this library to migrate from earlier, potentially abandoned giteas.
gitea >= 1.12.0 add paggination support ... - if you at the moment use the sdk in pagination mode it's very easy to get infinety loops with old versions
a nice edge case example:
A: say newer gitea paginate with 50 items
but you have a old non-paginating gitea with 50 issues ...
you can not detect by
if (len(item) < maxitem { break } else { next page }
if you have more than max items ... you can at least detect pagination is not working
ref #473
Asignee could be the first Asignees
Is there a different between all asignees and the first one for an issue/pull?
I have an idear how to avoid droping v1.11 support ... but get #473 let le have a look
3df7fcec02
to14379d1d2a
Drop deprecations & gitea <1.12.3 supportto Drop deprecations@zeripath I did left v1.11 support ...
@lunny the one field we drop finaly do not have any real value ... it's just because github had this in the past so it will stay in the api but the sdk do not have to support it since there is a clear migration path