@gitkraken/core-gitlens 0.9.2 → 0.9.4

package/CHANGELOG.md

@@ -6,6 +6,29 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 ## [Unreleased]
 
+## [0.9.4] - 2026-09-30
+
+### Added
+
+- Adds `state` (`'open' | 'closed' | 'all'`, omitted reads open) to the issue-tracker reads: `listIssueTrackerIssuesPage` and `IssuesIntegration.getIssuesForProject*`, reported as `getSupportedFilters().issueStates`. The trackers' account-wide read (`searchMyIssuesWithTruncationResult`'s `SearchMyIssuesOptions`) takes it too, though no facade read reaches that path yet. Linear, Jira and Jira Data Center narrow server-side on every page of their drains, so a project's done work no longer spends the page budget before its open issues. Trello can only read open cards, so it refuses `'closed'` and `'all'` with a warning and `fetchFailed` rather than serving the open ones. Every tracker also refuses a value outside the three (the integration reads too, before any request), and a cursor minted under one state when resumed under another (#5911) (plus/integrations)
+
+### Fixed
+
+- Fixes Linear issue reads listing completed and canceled issues. Both Linear list reads now default to open work, as every other tracker already did: pass `state: 'all'` to keep the old behavior, or `'closed'` for done work only. Bumps `@gitkraken/provider-apis` to 0.61.0, which carries the Linear state filter (#5911) (plus/integrations)
+- Fixes a Bitbucket Cloud pull request with a review bot among its participants (an `app_user` account, e.g. CodeAnt AI) failing the whole read. Bitbucket returns those accounts without `links.html` (and without a `nickname`), and the direct REST mapper read the link unguarded, so `getPullRequest`, `getPullRequestForBranch`, `getPullRequestsForBranch` (the whole list), `getIssueOrPullRequest` and `getPullRequestForCommit` threw. Such an account, as a participant, reviewer, author, issue reporter or assignee, now maps with no `url` (and no `avatarUrl` if Bitbucket sends none) ([#5910](https://github.com/gitkraken/vscode-gitlens/issues/5910)) (plus/integrations)
+
+## [0.9.3] - 2026-09-30
+
+### Added
+
+- Adds single pull request reads and URL identity parsing for Azure DevOps, Bitbucket Cloud and Bitbucket Data Center ([#5886](https://github.com/gitkraken/vscode-gitlens/issues/5886)). `Integration.getPullRequest(resource, id)` and `getPullRequestIdentityFromMaybeUrl(url)`, until now only implemented by GitHub and GitLab, resolve on these hosts too. Azure DevOps reads `{org}/{project}/_apis/git/pullrequests/{id}` — no repository required, since a pull request id is unique within the organization — with the project taken from the descriptor's `project` or else from a `{project}/_git/{repo}` or bare project name, and its URL parser decodes the path and anchors on `/_git/{repo}/pullrequest/{id}`, covering `dev.azure.com`, a Server address behind a virtual directory (dropped from the identity, so the connection's configured URL must include it), the legacy `{org}.visualstudio.com` host, and the short `{org}/_git/{repo}` form. Bitbucket Cloud and Data Center read through the strict by-id reads `getPullRequest` and `getServerPullRequest`, and their parsers accept `{workspace}/{repo}/pull-requests/{id}` and `projects/{KEY}/repos/{repo}/pull-requests/{id}` (a personal repository's `users/{slug}/repos/…` as project `~{slug}`), each rejecting the other's path shapes. Only a 404 resolves to `undefined`; every other failure reaches `getPullRequest`'s own error handling, so it is not cached as a miss (plus/integrations)
+
+### Fixed
+
+- Fixes a page-budgeted GitHub pull request sweep reporting its stop as an unrecoverable cap when the account has more than 1,000 matches — the search ceiling is now flagged only on the page where it ends the walk. This also changes an account-wide GitHub `listPullRequestsPage`: a page over the ceiling that can still continue no longer reports `page.truncated` or an `exhausted` warning, and only the page the ceiling ends on does (plus/git-github)
+- Fixes a pull request sweep that stopped at its page budget reporting it cannot be continued once any page was capped. A read that folds several searches into one page (GitHub's per-state facets) caps them independently, so one facet reaching the 1,000-result ceiling no longer hides a sibling that a bigger budget still reaches. This reverses 0.5.102's rule that a cap outranks a budget stop: a stop with a usable cursor is now always `page-budget`, and one drain can report two warnings, the `page-budget` one and, for the part paging could not reach, one with `recovery: 'none'` (or the SDK's own `provider-limit`, when the cap came from its metadata). A consumer that treated `page-budget` as proof the provider capped nothing must now check the drain's other warnings too (plus/integrations)
+- Fixes a tracker's project list (Jira and Jira Data Center projects and sites, Linear teams) being cached for the whole session, so a project created mid-session never appeared in `listIssueTrackerIssuesPage` or `listProjects` until a restart, and a deleted one kept being searched. The list is now dropped when the connection is re-synced (`refreshConnections()`, or `forceSync` on a read), including the copy Jira Cloud persisted for its next connect, and it expires after 5 minutes. A Jira search that fails because its project no longer exists or is no longer visible (`400` "does not exist for the field 'project'") now reads that project as empty and drops the stale list, instead of failing the whole provider on every read (#5907) (plus/integrations)
+
 ## [0.9.2] - 2026-09-30
 
 ### Added
@@ -468,7 +491,9 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 - Initial release. Bundles `@gitlens/utils`, `@gitlens/git`, `@gitlens/git-cli`, `@gitlens/ai`, and `@gitlens/git-github` into a single core npm package with subpath exports.
 
-[unreleased]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.2...HEAD
+[unreleased]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.4...HEAD
+[0.9.4]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.3...gitkraken:releases/core/v0.9.4
+[0.9.3]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.2...gitkraken:releases/core/v0.9.3
 [0.9.2]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.1...gitkraken:releases/core/v0.9.2
 [0.9.1]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.9.0...gitkraken:releases/core/v0.9.1
 [0.9.0]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.8.0...gitkraken:releases/core/v0.9.0

package/dist/plus/git-github/api/github.js

@@ -2043,7 +2043,7 @@ var GitHubApi = class {
 				values: rsp.search.nodes.map((pr) => options?.summary ? fromGitHubPullRequestLite(pr, provider) : fromGitHubPullRequest(pr, provider)),
 				cursor: rsp.search.pageInfo.endCursor ?? void 0,
 				hasMore: rsp.search.pageInfo.hasNextPage,
-				truncated: rsp.search.issueCount > githubSearchResultLimit
+				truncated: rsp.search.issueCount > 1e3 && !rsp.search.pageInfo.hasNextPage
 			};
 		} catch (ex) {
 			throw this.handleException(ex, provider, scope, options?.silent);