@gitkraken/provider-apis 0.52.0 → 0.54.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## 0.54.0
+
+- 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`
+- 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
+- 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
+- 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
+- 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
+- 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
+
+## 0.53.0
+
+- 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`
+- Added a `getIssuesForCurrentUser` method and `GetIssuesForCurrentUserInput` type to the `IssueProvider` contract so account-wide current-user issue reads share a common shape across providers
+- Added `getPullRequestsForReviewerAndWorkspace` to Bitbucket Cloud (which exposes no native workspace-level "PRs where this user is a reviewer" endpoint) by fanning out the existing repo-scoped reviewer query across either a provided repo subset or every accessible repo in the workspace
+- Added an optional `concurrency` parameter to the shared `collectAcrossScopes` util (routing the fan-out through `runInParallelBatches` to cap in-flight requests, defaulting to unbounded to preserve prior behavior) and wired a concurrency cap of 5 into every multi-scope PR fan-out (Bitbucket Cloud, Bitbucket Server, Azure DevOps repos and projects, Jira resources) to avoid thundering-herd rate limiting (429s) on large workspaces
+
 ## 0.52.0
 
 - Added common collection-result metadata (`metadata.completeness` and optional `metadata.failures`) to `Result<T>` / `PagedResult<T>` so callers can distinguish complete, partial, and unknown list/search results without inferring from pagination alone