@gitkraken/core-gitlens 0.9.2 → 0.9.4

package/dist/plus/integrations/integrationService.d.ts

@@ -2,7 +2,7 @@ import { Disposable } from "../../utils/disposable.js";
 import { Event } from "../../utils/event.js";
 import { RemoteProviderId } from "../../git/models/remoteProvider.js";
 import { GitRemote } from "../../git/models/remote.js";
-import { IssueSearchCriteria, IssueShape, IssueSorting } from "../../git/models/issue.js";
+import { IssueSearchCriteria, IssueShape, IssueSorting, IssueStateFilter } from "../../git/models/issue.js";
 import { PullRequest, PullRequestFilter, PullRequestSearchCriteria, PullRequestShape, PullRequestStateFilter } from "../../git/models/pullRequest.js";
 import { Account } from "../../git/models/author.js";
 import { GitHubApi } from "../git-github/api/github.js";
@@ -153,7 +153,8 @@ export declare class IntegrationService implements Disposable, RepositoryResolut
    * exchanged token rather than a possibly-stale cached one. Both paths refresh, by different mechanisms: a
    * per-connection (`connectionId`) read syncs that specific connection's session directly through the auth
    * provider (the integration's primary-only sync path would never reach a secondary account), while a
-   * primary read syncs via the integration's own cloud-connection machinery.
+   * primary read syncs via the integration's own cloud-connection machinery. Either way the integration's cached
+   * discovery (a tracker's project list) is dropped, so the read sees projects created or deleted since.
    * Best-effort — a failed sync is swallowed so the read still proceeds (and surfaces its own warning).
    */
   forceRefreshIfRequested(integration: Integration, forceSync: boolean | undefined, connectionId: string | undefined): Promise<void>;
@@ -396,6 +397,11 @@ export declare class IntegrationService implements Disposable, RepositoryResolut
      * is where a tracker reports; a key no normalized issue carries is refused for a multi-project page.
      */
     sort?: IssueSorting;
+    /**
+     * Which issue states to read. Omitted reads open issues. `'closed'`/`'all'` need
+     * `getSupportedFilters().issueStates` and are refused otherwise.
+     */
+    state?: IssueStateFilter;
     forceSync?: boolean;
     page?: number;
     cursor?: string;

package/dist/plus/integrations/integrationService.js

@@ -544,11 +544,13 @@ var IntegrationService = class {
 	* exchanged token rather than a possibly-stale cached one. Both paths refresh, by different mechanisms: a
 	* per-connection (`connectionId`) read syncs that specific connection's session directly through the auth
 	* provider (the integration's primary-only sync path would never reach a secondary account), while a
-	* primary read syncs via the integration's own cloud-connection machinery.
+	* primary read syncs via the integration's own cloud-connection machinery. Either way the integration's cached
+	* discovery (a tracker's project list) is dropped, so the read sees projects created or deleted since.
 	* Best-effort — a failed sync is swallowed so the read still proceeds (and surfaces its own warning).
 	*/
 	async forceRefreshIfRequested(integration, forceSync, connectionId) {
 		if (forceSync !== true) return;
+		integration.invalidateDiscoveryCaches();
 		try {
 			if (connectionId != null) {
 				const authProvider = await this.authenticationService.get(integration.authProvider.id);