@gitkraken/provider-apis 0.53.0 → 0.54.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,14 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.54.0
4
+
5
+ - Fixed Bitbucket Server pull-request numbered paging so `NumberedPageInput.page` is treated as a 1-based page number instead of a raw `start` offset; `pageInfo.nextPage` now returns the next page number to match `currentPage`
6
+ - Added `metadata.completeness` (`partial`) to GitHub's `searchPullRequests` and `searchIssues` when the query matches more than the 1000 results GitHub's search API will page through, so callers can tell a truncated search from a complete one instead of trusting `hasNextPage` alone; `getIssuesForUser` merges the completeness of its created/assigned sub-searches
7
+ - Added an optional `states` selector to GitHub's `getPullRequestsForUser` / `getIssuesForUser` and GitLab's `getPullRequestsForUser`, which previously dropped it and always returned open items regardless of the requested states
8
+ - Added `authorUsername` to GitLab's `getIssuesForCurrentUser` (`author_username` on the REST read, combinable with `assigneeUsername` under `scope: 'all'`); GitLab's endpoint exposes no mention filter, so mentions remain unsupported rather than approximated via search
9
+ - Changed `GetIssuesForCurrentUserInput` from a cursor/numbered union to a single interface extending both page inputs, so `scope` / `assigneeUsername` / `authorUsername` no longer require narrowing the union to be readable
10
+ - Raised GitHub's default PR search page size (`MAX_PR_PAGE_SIZE`) from 15 to 100 and routed both search reads through `resolvePageSize`, so an explicit `maxPageSize` is clamped to GitHub's maximum instead of being passed through verbatim
11
+
3
12
  ## 0.53.0
4
13
 
5
14
  - Added `getIssuesForCurrentUser` to GitLab (account-wide "my issues" read via REST `GET /issues`, since GitLab's GraphQL API exposes no top-level cross-project issue field): open issues only, with `scope` `'assigned_to_me'` (default, server-side user scoping) or `'all'` (every visible issue, optionally narrowed by `assigneeUsername`), and numbered pagination via `page`/`per_page` + `x-next-page`