@gitkraken/core-gitlens 0.23.0 → 0.25.0

package/CHANGELOG.md

@@ -6,6 +6,37 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 
 ## [Unreleased]
 
+## [0.25.0] - 2026-10-30
+
+### Added
+
+- Adds `Git.rev_parse__work_tree_of_git_dir(gitDir)`, resolving the working tree in `gitDir`'s parent folder that uses `gitDir` as its git dir, or `undefined` when none does (a bare repository) (git-cli)
+- Adds `scopeConcurrency?: number` to `IntegrationManager.listPullRequestsPage` (repo-scoped reads only), `listIssuesPage`, and `sweepPullRequests`/`sweepClosedPullRequests`, setting the most per-repository requests (per-project for Azure DevOps issues) one provider read keeps in flight. Defaults to 6; a value that isn't a finite number of at least 1 falls back to the default, and a fraction is truncated. A sweep runs up to 6 targets at once, each with this bound (plus/integrations)
+- Adds `includeRemoteInfo?: boolean` to `IntegrationManager.listPullRequestsPage` (repo-scoped reads only) and `sweepPullRequests`/`sweepClosedPullRequests` (repo-scoped targets), an opt-out for the Azure DevOps lookup that fills each row's clone URLs. `false` saves one request per repository (and fork source) per page, at the cost of rows carrying no `refs.base.url`/`refs.head.url` (empty) and no `cloneHttps`/`cloneSsh`. Defaults to `true`, the existing behavior; other providers ignore it (plus/integrations)
+- Adds several targets per provider to `IntegrationManager.sweepPullRequests`/`sweepClosedPullRequests`, one per connection (for example two GitHub Enterprise installations, two Bitbucket Data Center servers or two github.com accounts): `targets` now accepts any number of `ProviderSweepTarget`s of one provider as long as each names a `connectionId` or, on a self-managed host, a `domain`, and a repeat (matched by host however its `domain` is spelled) or an unnamed target beside a named one of the same provider throws a `TypeError`. `ProviderSweepTarget.repos` gives each target its own repositories, overriding the sweep-level `repos` (an empty array reads that target account-wide), and `ProviderSweepResult.failedTargets`/`incompleteTargets` (`ProviderSweepTargetRef[]`: `providerId`, `connectionId`, resolved `domain`) attribute failures per connection, with `failedProviderIds` now listing a provider only when every one of its targets failed and `incompleteProviderIds` any provider with a failed or incomplete target beside one that returned. A sweep with one target per provider is unchanged (plus/integrations)
+- Adds the `plus/notifications` subpaths (`context.js`, `errors.js`, `models.js`, `notificationsService.js` and `presentation.js`): a client and state holder for GitKraken `notifications-service-v2` notifications filtered by product, with a host-implemented `NotificationsContext`. See [`docs/notifications.md`](./docs/notifications.md) (plus/notifications)
+
+### Changed
+
+- Bounds the repository and project fan-out of repo-scoped pull request and issue reads (`listPullRequestsPage`, `listIssuesPage` and the pull request sweeps) to 6 requests in flight, instead of one request per repository at once. This applies to the hosts that read repository by repository: pull requests on GitLab, GitLab self-managed, Bitbucket Cloud, Bitbucket Data Center and Azure DevOps, and issues on GitLab, GitLab self-managed and Azure DevOps (per project). Results, ordering and per-repository failure isolation are unchanged; GitHub/GHE already send one query whatever the repo count (plus/integrations)
+
+### Fixed
+
+- Fixes self-managed integration reauthentication disconnecting other connections of the same provider: forced reauthentication now validates and disconnects only the selected connection's token (plus/integrations)
+- Fixes `getRepositoryInfo` (and `Git.rev_parse__show_toplevel`) resolving a path inside a repository's `.git` folder — `.git/refs`, `.git/rebase-merge` during a rebase — to that `.git` folder as a bare repository when the repo's config has no `core.bare` line, so a host registered it as a second repository named `.git`. Git guesses "bare" from inside a git dir when `core.bare` is unset; a git dir whose parent folder is a working tree using it now resolves to that working tree. Real bare repos, including a bare clone named `.git` beside its worktrees and a `.bare` folder behind a `.git` file, still resolve to themselves (git-cli)
+- Fixes Bitbucket Data Center repo-scoped pull request reads (`listPullRequestsPage` with `repos` and the pull request sweeps with `repos`) reading only the first page of each repository: a repository with more open pull requests than one page (50 by default) came back `page.truncated` and was never continued, and `page: 2` re-read page 1. Bitbucket Data Center now reads repository by repository like the other numbered hosts, with a continuation cursor per repository, `page` honored, the 6-in-flight bound, and a failed repository attributed as its own scope with its cause (plus/integrations)
+- Fixes GitHub GraphQL throttling (HTTP 200 with an `errors` entry of type `RATE_LIMITED` or `RATE_LIMIT`) being reported as `kind: 'other'` instead of `'rate-limit'` on repo-scoped GitHub and GitHub Enterprise pull request and issue reads (`listPullRequestsPage`, `listIssuesPage` and the pull request sweeps with `repos`), which provider-apis serves and throws without a response status. Core's own GitHub reads now also classify a rate limit that isn't the first GraphQL error (plus/integrations, plus/git-github)
+- Fixes one connection's failed requests disconnecting another connection of the same provider: an integration counted the failures that disconnect it after five (a 4xx, a server error or timeout, or a refused token its forced refresh could not recover) in one budget shared by every connection it reads, so a secondary account read by `connectionId` (e.g. a second target of one provider in `sweepPullRequests`) failing five times dropped the primary account's session and announced the disconnect, and a success on any connection wiped every other connection's count. The budget is now per connection: a read naming the primary's `connectionId` shares the primary's, only the primary's limit disconnects, and a secondary that reaches it keeps reporting each failure on its own reads (plus/integrations, git, plus/git-github)
+- Fixes `getIgnoredPaths` throwing for the whole batch when git refuses one path in it, such as a path beyond a symlink (`fatal: pathspec '...' is beyond a symbolic link`), inside a submodule, outside the repository, or empty. Git answers every path before the one it refuses, so only the paths after it are asked again, less the rest of a folder refused for a symlink or submodule: a refused path counts as not ignored, even alone, and each path is answered once, in one `check-ignore` run plus one per refusal. It still rejects, after one run, when git fails for any other reason, and on cancellation (git-cli)
+- Fixes `fetch`, `pull` and `push` with a remote-tracking branch reference that carries an `upstream` (as a host's remote branch refs may, with the remote's own name) using that name as the branch to fetch or push to, e.g. `git fetch upstream upstream`: `getBranchTrackingWithoutRemote` now returns `undefined` for a remote-tracking branch, and `fetch` reads the branch's own name (git, git-cli)
+- Fixes a git command that fails to launch, such as one run in a folder that no longer exists, keeping the Node process alive for the full git timeout (60 seconds by default): Node clears a spawn's timeout timer only when the process exits, which a failed launch never does, so a short-lived host could hang before exiting. The default spawner now also clears it when the process closes, as Node itself does in [nodejs/node#65506](https://github.com/nodejs/node/pull/65506). A custom `spawn` still receives `timeout` and handles it itself ([#6105](https://github.com/gitkraken/vscode-gitlens/pull/6105)) (git-cli)
+
+## [0.24.0] - 2026-10-28
+
+### Changed
+
+- Changes Linear's user-scoped tracker read (`listIssueTrackerIssuesPage` without `includeAllAssignees`, and `IssuesIntegration.getIssuesForProject*` with `options.user`) to also return the GitHub-synced issues the viewer created, not only those assigned to them. Linear's two-way GitHub Issues sync makes the author of a GitHub issue (one who linked their GitHub account to Linear) the creator of its Linear copy but assigns no one the GitHub issue doesn't, so the Linear copy of a GitHub issue the user filed was never read and a host showed only its GitHub copy. Only issues with a GitHub issue attachment and a GitHub sync link (`syncedWith` not `[]`) widen, so the rest of what the viewer created in Linear stays out; a synced row whose link list Linear failed to resolve is kept rather than silently dropped. Asking for `filters: [IssueFilter.Assignee]` by name still reads only assigned issues. Still one query per page; the wider match can take more pages. Requires `@gitkraken/provider-apis` with `LinearGetIssuesInput.githubSyncedCreators`; an older one ignores it and reads assigned issues only ([gitkraken/kepler#4480](https://github.com/gitkraken/kepler/issues/4480)) (plus/integrations)
+
 ## [0.23.0] - 2026-10-28
 
 ### Added
@@ -1017,7 +1048,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.23.0...HEAD
+[unreleased]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.25.0...HEAD
+[0.25.0]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.24.0...gitkraken:releases/core/v0.25.0
+[0.24.0]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.23.0...gitkraken:releases/core/v0.24.0
 [0.23.0]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.22.1...gitkraken:releases/core/v0.23.0
 [0.22.1]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.22.0...gitkraken:releases/core/v0.22.1
 [0.22.0]: https://github.com/gitkraken/vscode-gitlens/compare/releases/core/v0.21.0...gitkraken:releases/core/v0.22.0

package/README.md

@@ -2,18 +2,19 @@
 
 Shared Git, AI, and GitHub primitives from [GitLens](https://github.com/gitkraken/vscode-gitlens), bundled for consumption by internal GitKraken products.
 
-This package flattens eight internal workspace packages into a single tarball:
-
-| Subpath               | Source package          | License        |
-| --------------------- | ----------------------- | -------------- |
-| `utils/*`             | `@gitlens/utils`        | See `LICENSE`  |
-| `ipc/*`               | `@gitlens/ipc`          | See `LICENSE`  |
-| `git/*`               | `@gitlens/git`          | See `LICENSE`  |
-| `git-cli/*`           | `@gitlens/git-cli`      | See `LICENSE`  |
-| `plus/ai/*`           | `@gitlens/ai`           | `LICENSE.plus` |
-| `plus/git-github/*`   | `@gitlens/git-github`   | `LICENSE.plus` |
-| `plus/agents/*`       | `@gitlens/agents`       | `LICENSE.plus` |
-| `plus/integrations/*` | `@gitlens/integrations` | `LICENSE.plus` |
+This package flattens nine internal workspace packages into a single tarball:
+
+| Subpath                | Source package           | License        |
+| ---------------------- | ------------------------ | -------------- |
+| `utils/*`              | `@gitlens/utils`         | See `LICENSE`  |
+| `ipc/*`                | `@gitlens/ipc`           | See `LICENSE`  |
+| `git/*`                | `@gitlens/git`           | See `LICENSE`  |
+| `git-cli/*`            | `@gitlens/git-cli`       | See `LICENSE`  |
+| `plus/ai/*`            | `@gitlens/ai`            | `LICENSE.plus` |
+| `plus/git-github/*`    | `@gitlens/git-github`    | `LICENSE.plus` |
+| `plus/agents/*`        | `@gitlens/agents`        | `LICENSE.plus` |
+| `plus/integrations/*`  | `@gitlens/integrations`  | `LICENSE.plus` |
+| `plus/notifications/*` | `@gitlens/notifications` | `LICENSE.plus` |
 
 ## Usage
 
@@ -37,6 +38,13 @@ provider-neutral facade at `plus/integrations/index.js`. It has its own guide
 warning contracts, the filter capability table, and a per-provider capability matrix:
 [`docs/integrations.md`](./docs/integrations.md).
 
+### Notifications
+
+Showing GitKraken notifications (the `notifications-service-v2` inbox) in another host goes through
+`plus/notifications/notificationsService.js` and its host context. Its guide covers implementing the context, the
+refresh and toast contracts, and what the host must own (polling, persistence, toast de-duplication, safe link
+handling): [`docs/notifications.md`](./docs/notifications.md).
+
 ### Node vs browser
 
 `utils/` uses internal `#env/*` imports that resolve differently based on the target:
@@ -53,7 +61,7 @@ The package is marked `"sideEffects": false` and uses per-file subpath exports.
 ## Licensing
 
 - `LICENSE` — governs `utils/`, `git/`, and `git-cli/`.
-- `LICENSE.plus` — governs everything under `plus/` (currently `plus/ai/`, `plus/git-github/`, `plus/agents/`, and `plus/integrations/`). Proprietary; not for redistribution.
+- `LICENSE.plus` — governs everything under `plus/` (currently `plus/ai/`, `plus/git-github/`, `plus/agents/`, `plus/integrations/`, and `plus/notifications/`). Proprietary; not for redistribution.
 
 ## Versioning
 
@@ -63,8 +71,8 @@ Independent from the [GitLens VS Code extension](https://github.com/gitkraken/vs
 
 Built from the `packages/` workspace of [vscode-gitlens](https://github.com/gitkraken/vscode-gitlens), by `pnpm --filter @gitkraken/core-gitlens run build` in two steps:
 
-1. **`tsdown.config.ts`** compiles the eight packages' TypeScript sources straight into `dist/`, one emitted module per source module, each rooted at the subpath in the table above. It reads their `src/` directly — the packages' own manifests resolve to source, so nothing here waits on their `dist/` — and cross-package imports come out as relative paths, with `#env/*` staying external for the `"imports"` field to resolve.
-2. **`scripts/bundle.mjs`** assembles everything around that: it copies the LICENSEs and generates the manifest's `exports`, `imports`, and `dependencies` from the eight sub-packages' own manifests.
+1. **`tsdown.config.ts`** compiles the nine packages' TypeScript sources straight into `dist/`, one emitted module per source module, each rooted at the subpath in the table above. It reads their `src/` directly — the packages' own manifests resolve to source, so nothing here waits on their `dist/` — and cross-package imports come out as relative paths, with `#env/*` staying external for the `"imports"` field to resolve.
+2. **`scripts/bundle.mjs`** assembles everything around that: it copies the LICENSEs and generates the manifest's `exports`, `imports`, and `dependencies` from the nine sub-packages' own manifests.
 
 Neither the subpath layout nor the generated manifest is hand-written, so adding or removing a bundled package is a one-line change to `scripts/packages.mjs`, which both steps read.
 

package/dist/git/errors.d.ts

@@ -447,12 +447,13 @@ export declare class RequestRateLimitError extends Error {
   constructor(original: Error, token: string | undefined, resetAt: number | undefined);
 }
 /**
- * Spends `provider`'s strike toward disconnecting for a request that failed with a server error or timed out, and
- * shows `notify`'s notice; or, with `defer`, leaves both to the batch read that made the request, which counts its
- * failed requests once for the whole call (see {@link getDeferredRequestFailure}). A batch fans out into a request
- * per target, so one outage would otherwise disconnect the integration in the middle of a batch.
+ * Spends a strike toward disconnecting `provider`'s connection `connectionId` (the one whose token made the request;
+ * the primary when omitted) for a request that failed with a server error or timed out, and shows `notify`'s notice;
+ * or, with `defer`, leaves both to the batch read that made the request, which counts its failed requests once for
+ * the whole call (see {@link getDeferredRequestFailure}). A batch fans out into a request per target, so one outage
+ * would otherwise disconnect the integration in the middle of a batch.
  */
-export declare function reportRequestFailure(provider: Provider | undefined, ex: Error, notify: () => void, defer: boolean | undefined): void;
+export declare function reportRequestFailure(provider: Provider | undefined, ex: Error, notify: () => void, defer: boolean | undefined, connectionId: string | undefined): void;
 /** The notice a failed request left to its batch read (see {@link reportRequestFailure}), if it left one. */
 export declare function getDeferredRequestFailure(ex: unknown): (() => void) | undefined;
 export type SigningErrorReason = 'noKey' | 'gpgNotFound' | 'sshNotFound' | 'passphraseFailed' | 'unknown';

package/dist/git/errors.js

@@ -960,17 +960,18 @@ var RequestRateLimitError = class RequestRateLimitError extends Error {
 };
 const deferredRequestFailures = /* @__PURE__ */ new WeakMap();
 /**
-* Spends `provider`'s strike toward disconnecting for a request that failed with a server error or timed out, and
-* shows `notify`'s notice; or, with `defer`, leaves both to the batch read that made the request, which counts its
-* failed requests once for the whole call (see {@link getDeferredRequestFailure}). A batch fans out into a request
-* per target, so one outage would otherwise disconnect the integration in the middle of a batch.
+* Spends a strike toward disconnecting `provider`'s connection `connectionId` (the one whose token made the request;
+* the primary when omitted) for a request that failed with a server error or timed out, and shows `notify`'s notice;
+* or, with `defer`, leaves both to the batch read that made the request, which counts its failed requests once for
+* the whole call (see {@link getDeferredRequestFailure}). A batch fans out into a request per target, so one outage
+* would otherwise disconnect the integration in the middle of a batch.
 */
-function reportRequestFailure(provider, ex, notify, defer) {
+function reportRequestFailure(provider, ex, notify, defer, connectionId) {
 	if (defer) {
 		deferredRequestFailures.set(ex, notify);
 		return;
 	}
-	provider?.trackRequestException();
+	provider?.trackRequestException({ connectionId });
 	notify();
 }
 /** The notice a failed request left to its batch read (see {@link reportRequestFailure}), if it left one. */