@gitkraken/provider-apis 0.51.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.
Files changed (15) hide show
  1. package/CHANGELOG.md +15 -0
  2. package/dist/index.js +181 -181
  3. package/dist/index.provider-utils.js +1 -1
  4. package/dist/index.providers.js +167 -167
  5. package/dist/providers/azureDevops/azureDevOps.d.ts +2 -0
  6. package/dist/providers/bitbucket/bitbucket.d.ts +15 -1
  7. package/dist/providers/bitbucketServer/bitbucketServer.d.ts +1 -0
  8. package/dist/providers/gitlab/gitlab.d.ts +14 -2
  9. package/dist/providers/issueProvider.d.ts +2 -1
  10. package/dist/providers/jira/jira.d.ts +2 -0
  11. package/dist/providers/trello/trello.d.ts +1 -0
  12. package/dist/types/exportedTypes/issueProvider.d.ts +5 -1
  13. package/dist/types/exportedTypes/types.d.ts +38 -0
  14. package/dist/utils.d.ts +50 -2
  15. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,20 @@
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
+
10
+ ## 0.52.0
11
+
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
13
+ - Jira `getJiraProjectsForResources`, Bitbucket / Bitbucket Server / Azure DevOps multi-repo PR fan-outs, and Azure DevOps multi-project PR fan-out now preserve completeness and structured per-scope failures while keeping their existing `data` payloads backward compatible
14
+ - Multi-scope fan-outs now surface per-scope auth, rate-limit, provider, and network failures in `metadata.failures`, and may degrade to partial or empty aggregate results instead of throwing when some requested scopes fail
15
+ - Trello's `getIssuesForBoard` now sets `metadata.completeness` (`unknown` when the result hits the `/1/search` `cards_limit` cap, `complete` otherwise), so callers can tell a complete board read from a possibly-truncated one; Trello exposes no truncation flag or cursor, so hitting the cap is the only omission signal and no fake `hasNextPage`/cursor is invented; existing consumers reading only `data` are unaffected
16
+ - Extracted the duplicated multi-scope fan-out completeness/failure aggregation into a shared `collectAcrossScopes` util (internal refactor, no change to any provider's fan-out behavior or public contract)
17
+
3
18
  ## 0.51.0
4
19
 
5
20
  - Fixed GitLab `getPullRequestDiff` failing on some self-managed instances that return `500 Internal Server Error` from the `/merge_requests/:iid/diffs` endpoint for large `per_page` values, by paging that endpoint in smaller chunks (with a higher page cap to preserve the overall diff-entry budget); also hardened `fetchAllPagedGitLabREST` to stop when `x-next-page` does not advance