@gitkraken/provider-apis 0.52.0 → 0.53.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 +7 -0
- package/dist/index.js +121 -121
- package/dist/index.provider-utils.js +1 -1
- package/dist/index.providers.js +142 -142
- package/dist/providers/bitbucket/bitbucket.d.ts +14 -1
- package/dist/providers/gitlab/gitlab.d.ts +14 -2
- package/dist/providers/issueProvider.d.ts +2 -1
- package/dist/types/exportedTypes/issueProvider.d.ts +5 -1
- package/dist/utils.d.ts +7 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.53.0
|
|
4
|
+
|
|
5
|
+
- 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`
|
|
6
|
+
- Added a `getIssuesForCurrentUser` method and `GetIssuesForCurrentUserInput` type to the `IssueProvider` contract so account-wide current-user issue reads share a common shape across providers
|
|
7
|
+
- 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
|
|
8
|
+
- 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
|
|
9
|
+
|
|
3
10
|
## 0.52.0
|
|
4
11
|
|
|
5
12
|
- 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
|