@gitkraken/core-gitlens 0.16.1 → 0.16.2

package/dist/plus/integrations/reads/drains.d.ts

@@ -2,7 +2,6 @@ import { ResourceDescriptor } from "../../../git/models/resourceDescriptor.js";
 import { PullRequest, PullRequestFilter, PullRequestStateFilter } from "../../../git/models/pullRequest.js";
 import { IntegrationIds } from "../constants.js";
 import { ProviderWarning } from "../results.js";
-import "../providerFilters.js";
 import { ProviderPullRequest, ProviderReposInput, ProviderRepository } from "../providers/models.js";
 import { GitHostIntegration } from "../models/gitHostIntegration.js";
 import { IssuesIntegration } from "../models/issuesIntegration.js";

package/docs/integrations.md

@@ -1285,8 +1285,8 @@ Linear reports its canceled and duplicate states as `CANCELED`.
 Azure DevOps reports a state in its `Removed` category as `CANCELED`, `Completed` and `Resolved` as `DONE`,
 `InProgress` as `IN_PROGRESS` and `Proposed` as `TO_DO`. No work item read carries the category, so every one (by id,
 the cheap etag check and the project list, on Azure DevOps Server too) classifies its rows from their type's states
-(`GET …/_apis/wit/workItemTypes/{type}/states?api-version=6.0-preview.1`, the preview version Azure DevOps Server 2020
-requires), keyed on the raw `System.State`, and caches each read for five minutes per host, project, type and
+(`GET …/_apis/wit/workItemTypes/{type}/states`, with a version selected from the installation's REST resource metadata;
+Services and Server 2020 use `6.0-preview.1`), keyed on the raw `System.State`, and caches each read for five minutes per host, project, type and
 credential. The category, never the name, decides: a state named `Canceled` in the `Completed` category is `DONE`, and
 a state its type doesn't list has no category. When a states read fails, a project list keeps its rows (the failed
 type's without a category) and reports the project as a partial collection with a failure scoped to it; a read by id
@@ -1296,14 +1296,25 @@ or resolved dates. Failed workflows fall back to dates with partial metadata; fa
 before retrying. List, identity and native presentation reads share one cache, including workflow expiry and HTTP
 proxy invalidation.
 
+TFS 2018 uses its advertised REST versions and collection-level work item routes. A work item must report the
+requested project, so a collection-level read cannot answer for another project's coordinate. If the type's states
+omit categories, core supplements them from the project's `backlogconfiguration.workItemTypeMappedStates`, using
+only explicit type/state pairs. Unmapped states, including Removed on some processes, remain unknown; neither
+state names, colors nor absence from the backlog imply a category. A point or etag read of such a state fails.
+Project lists retain mapped row categories and report incomplete workflows as partial collections; selection for
+an incomplete workflow retains the SDK's date fallback. Exact state-filtered searches and counts refuse incomplete
+workflow metadata. `criteria.state: 'all'` skips that selection requirement, although search hydration still fails
+if a returned row's state has no category. Legacy identity strings remain opaque values, never inferred GUIDs.
+
 `listIssuesPage` accepts `state: 'open' | 'closed' | 'all'` for Azure DevOps Services and Server, on repository,
 project and account-wide reads. Omitted means open only. `getSupportedFilters(providerId).issueStates` declares this
 capability. Other git hosts retain their open-only list default and refuse non-open state requests on this facade.
 
 A known Azure workflow category determines normalized `state` and `closed`, with `CANCELED` closing like `DONE`.
 A historical closed date remains available as data but does not close an issue whose category is now open.
-Identity and list reads fall back to the closed date only when the category is unknown. Other providers keep their
-existing derivation.
+Identity and list reads fall back to the closed date only when the category is unknown. Legacy workflows that
+needed backlog mappings instead refuse point reads and cheap etag checks for an absent or uncategorized current
+state, even when all returned states received mappings. Other providers keep their existing derivation.
 
 ### Sprints and iterations
 
@@ -1341,14 +1352,17 @@ Two exceptions carry HTML with `bodyFormat` omitted: Azure DevOps work items and
 (`content.html`). Their `bodyFormat` is left unset rather than changed, so check the provider before treating either
 as Markdown.
 
-An Azure DevOps work item's body is its first rich text field with content, since its type decides where the content
-lives: `System.Description`, then the built-in description fields (`Microsoft.VSTS.TCM.ReproSteps` on Agile, Scrum and
-CMMI Bugs, `Microsoft.VSTS.Common.AcceptanceCriteria`, `Microsoft.VSTS.CMMI.Symptom`), then any other `html` field
-of the organization's field catalog, custom fields first (provider-apis' `getAzureWorkItemDescription`, which every
-read applies). `bodyField` names the field (`{ id: 'Microsoft.VSTS.TCM.ReproSteps', name: 'Repro Steps' }`) so a
-host can label the body; it is absent for other providers. The catalog is read only for a work item no built-in field
-describes, and kept for an hour per organization, credential and client (provider-apis keeps its own for list rows); when it can't be read the body falls back to the built-in
-fields.
+An Azure DevOps work item's body is its first rich text field with content: `System.Description`, then the built-in
+description fields (`Microsoft.VSTS.TCM.ReproSteps`, `Microsoft.VSTS.Common.AcceptanceCriteria`,
+`Microsoft.VSTS.CMMI.Symptom`), then additional HTML fields declared by the organization's field catalog, custom fields
+first. Every read uses provider-apis' shared selector. `bodyField` names the selected field
+(`{ id: 'Microsoft.VSTS.TCM.ReproSteps', name: 'Repro Steps' }`) so a host can label the body; it is absent when no body
+is available and for other providers. The catalog is read only when no built-in field describes the work item, and
+kept for an hour per organization, credential and client (provider-apis keeps its own for list rows). An unavailable
+or malformed catalog leaves the body to the built-in fields rather than failing the work item; the caller's
+cancellation still propagates.
+An empty Description is preserved when no field has visible content. Direct reads share a catalog cache scoped to
+the installation, collection, credential and authentication mode, cleared on HTTP proxy changes.
 
 Rendering and conversion remain consumer concerns. In particular, the Jira body is neither ADF nor converted to
 Markdown by this package.
@@ -1433,7 +1447,10 @@ Markdown by this package.
     replaces it. A continuation whose snapshot is gone is refused (warning + `fetchFailed`) rather than resumed
     against a fresh query, where an item moved by the `updated` order could be skipped. Restart without the cursor.
     A cursor is bound to its query and refused under another one. `page` without a cursor walks from page 1 against
-    a fresh query. Requests use REST `api-version=5.0`, so Azure DevOps Server 2019 or later is required.
+    a fresh query. Requests negotiate REST versions from the installation's resource metadata, including TFS 2018.
+    Exact state-filtered searches and counts require complete workflow categories; `state: 'all'` skips that
+    selection requirement, but every hydrated row in a legacy workflow that needed backlog mappings still needs an
+    authoritative category.
   - **Pull requests** (`searchPullRequestsPage` / `countPullRequests`) drain every facet — each repository, or each
     project of the `org` (every visible project when only relationships bound the search), times each
     relationship — reading up to 1,000 pull requests per facet, then apply text, draft and dates, union by repository

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@gitkraken/core-gitlens",
   "description": "GitLens core — shared Git / AI / GitHub primitives for internal GitKraken consumption",
-  "version": "0.16.1",
+  "version": "0.16.2",
   "license": "SEE LICENSE IN LICENSE",
   "author": {
     "name": "GitKraken",
@@ -239,7 +239,7 @@
     }
   },
   "dependencies": {
-    "@gitkraken/provider-apis": "0.65.4",
+    "@gitkraken/provider-apis": "0.65.5",
     "@octokit/graphql": "9.0.4",
     "@octokit/request": "10.0.14",
     "@octokit/request-error": "7.1.1",