@gitkraken/provider-apis
Azure DevOps issue listings, workflow metadata and pull-request detail reads support Azure DevOps Services,
Azure DevOps Server 2020 and TFS 2018. Self-hosted reads discover each resource's supported REST version and
project route through authenticated OPTIONS requests. TFS 2018 work-item hydration uses collection-level
GET requests when the server does not advertise the batch endpoint; returned projects are checked before
normalization. Authentication failures and missing resources propagate without version retries.
AzureDevOps.getRestApiResource({ namespace, resource, version? }, options) exposes the same negotiation to
consumers with direct REST reads. It returns { apiVersion, projectScoped }, or undefined when discovery
succeeds but the resource is absent. Discovery is shared per client, collection, resource area and credential;
updateConfig clears it. Azure DevOps Services keeps the existing REST versions without discovery.
Each read captures its URL, authentication, transport and discovery cache before awaiting any responses,
so an in-flight read finishes against the installation it started with when configuration changes.
This compatibility applies to these reads, not every SDK mutation or endpoint.
Legacy workflow states can omit WorkItemState.category. The SDK preserves that absence, and state-filtered
listings retain the existing date fallback with partial metadata when a complete category snapshot is
unavailable. Consumers can supply authoritative categories with workItemTypeStates. Legacy identity strings
are preserved as opaque account identifiers and labels; they do not establish equality with a current-user GUID.