@gitkraken/provider-apis 0.50.0 → 0.52.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 +12 -0
- package/dist/index.js +175 -175
- package/dist/index.provider-utils.js +1 -1
- package/dist/index.providers.js +168 -168
- package/dist/providers/azureDevops/azureDevOps.d.ts +2 -0
- package/dist/providers/bitbucket/bitbucket.d.ts +1 -0
- package/dist/providers/bitbucketServer/bitbucketServer.d.ts +1 -0
- package/dist/providers/jira/jira.d.ts +2 -0
- package/dist/providers/trello/trello.d.ts +1 -0
- package/dist/types/exportedTypes/types.d.ts +38 -0
- package/dist/utils.d.ts +44 -2
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.52.0
|
|
4
|
+
|
|
5
|
+
- 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
|
|
6
|
+
- 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
|
|
7
|
+
- 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
|
|
8
|
+
- 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
|
|
9
|
+
- 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)
|
|
10
|
+
|
|
11
|
+
## 0.51.0
|
|
12
|
+
|
|
13
|
+
- 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
|
|
14
|
+
|
|
3
15
|
## 0.50.0
|
|
4
16
|
|
|
5
17
|
- Added an optional `states` selector to PR/issue list inputs across GitHub, GitLab, Bitbucket, Bitbucket Server, Azure DevOps, and Jira, honored per provider without changing the default (open-only) behavior
|