[Automated] Update ATS API Surface Area

[aspire-repo-bot]

Auto-generated update to the ATS (Aspire Type System) capability surface to compare current surface vs latest release. This should only be merged once this surface area ships in a new release.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 18339

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 18339"

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 5 comments.

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (4)

src/Aspire.Hosting.Foundry/api/Aspire.Hosting.Foundry.ats.txt:59

• The exported model Name value uses an uppercase Cohere- prefix, while the existing Cohere model just above uses lowercase (\"cohere-command-a\"). If the backing service treats model names as case-sensitive (common for IDs), this would cause runtime failures. Align the casing with the established naming convention used for other Cohere entries in this file.

FoundryModels.Cohere.CohereCommandAPlus052026: Aspire.Hosting.Foundry/Aspire.Hosting.Foundry.FoundryModel = {"Name":"Cohere-command-a-plus-05-2026","Version":"1","Format":"Cohere"}

src/Aspire.Hosting.Kubernetes/api/Aspire.Hosting.Kubernetes.ats.txt:110

• The withPv* method names introduce an abbreviation (Pv) that is inconsistent with nearby capability naming (e.g., withIngressTlsParam, withLetsEncryptStagingParam) and is less discoverable in IntelliSense/search. Prefer fully spelled names (e.g., withPersistentVolumeCapacityParam, withPersistentVolumeStorageClassParam) before this API shape becomes widely consumed.

Aspire.Hosting.Kubernetes/withPvCapacityParam(capacity: Aspire.Hosting/Aspire.Hosting.ApplicationModel.ParameterResource) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource
Aspire.Hosting.Kubernetes/withPvStorageClassParam(storageClassName: Aspire.Hosting/Aspire.Hosting.ApplicationModel.ParameterResource) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource

src/Aspire.Hosting.Radius/api/Aspire.Hosting.Radius.ats.txt:12

• withContainerImage is emitted under the Aspire.Hosting.Radius/ capability namespace but returns Aspire.Hosting.ApplicationModel.ProjectResource, unlike the other Radius fluent APIs that return RadiusEnvironmentResource. This looks like a mis-generated/incorrect capability signature (either wrong return type or wrong capability namespace), and could break tooling that assumes fluent calls stay within the Radius resource chain.

Aspire.Hosting.Radius/withContainerImage(image: string) -> Aspire.Hosting/Aspire.Hosting.ApplicationModel.ProjectResource
Aspire.Hosting.Radius/withNamespace(kubernetesNamespace: string) -> Aspire.Hosting.Radius/Aspire.Hosting.Radius.RadiusEnvironmentResource

src/Aspire.Hosting.Dotnet/api/Aspire.Hosting.Dotnet.ats.txt:8

• The handle type and return type are emitted as Aspire.Hosting.Dotnet/Aspire.Hosting.ApplicationModel.DotnetProjectResource, mixing the package prefix (Aspire.Hosting.Dotnet/) with a type name rooted in Aspire.Hosting.ApplicationModel. If this is intended, it may still be confusing for ATS consumers and can complicate mapping types back to assemblies/namespaces; consider emitting a consistent fully-qualified type identity (package + type) that matches how other ATS files represent their handle types.

Aspire.Hosting.Dotnet/Aspire.Hosting.ApplicationModel.DotnetProjectResource [ExposeProperties]

# Capabilities
Aspire.Hosting.Dotnet/addDotnetProject(name: string, path: string, options?: Aspire.Hosting/Aspire.Hosting.ProjectResourceOptions) -> Aspire.Hosting.Dotnet/Aspire.Hosting.ApplicationModel.DotnetProjectResource

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (4)

src/Aspire.Hosting.Go/api/Aspire.Hosting.Go.ats.txt:10

• Parameter name acceptMulticlient has inconsistent casing for the compound word (typically MultiClient / multiclient conventions). Consider renaming to acceptMultiClient to align with standard .NET/camelCase naming and improve discoverability.

Aspire.Hosting.Go/withDelveServer(port?: number, acceptMulticlient?: boolean, onlySameUser?: boolean, continueOnStart?: boolean, log?: boolean, logOutput?: string) -> Aspire.Hosting.Go/Aspire.Hosting.Go.GoAppResource

src/Aspire.Hosting.Kubernetes/api/Aspire.Hosting.Kubernetes.ats.txt:63

• The naming for PersistentVolume parameter-based setters is inconsistent: withCapacity pairs with withPvCapacityParam (extra Pv prefix), and withStorageClass pairs with withPvStorageClassParam. This asymmetry makes the API harder to guess. Consider aligning the pair names (e.g., withCapacity + withCapacityParam, withStorageClass + withStorageClassParam) or consistently including/excluding the Pv prefix for both variants.

Aspire.Hosting.Kubernetes/withCapacity(capacity: string) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource

src/Aspire.Hosting.Kubernetes/api/Aspire.Hosting.Kubernetes.ats.txt:112

• The naming for PersistentVolume parameter-based setters is inconsistent: withCapacity pairs with withPvCapacityParam (extra Pv prefix), and withStorageClass pairs with withPvStorageClassParam. This asymmetry makes the API harder to guess. Consider aligning the pair names (e.g., withCapacity + withCapacityParam, withStorageClass + withStorageClassParam) or consistently including/excluding the Pv prefix for both variants.

Aspire.Hosting.Kubernetes/withPvCapacityParam(capacity: Aspire.Hosting/Aspire.Hosting.ApplicationModel.ParameterResource) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource
Aspire.Hosting.Kubernetes/withPvStorageClassParam(storageClassName: Aspire.Hosting/Aspire.Hosting.ApplicationModel.ParameterResource) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource
Aspire.Hosting.Kubernetes/withServicePort(port?: number) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesAspireDashboardResource
Aspire.Hosting.Kubernetes/withStorageClass(storageClassName: string) -> Aspire.Hosting.Kubernetes/Aspire.Hosting.Kubernetes.KubernetesPersistentVolumeResource

src/Aspire.Hosting.Foundry/api/Aspire.Hosting.Foundry.ats.txt:59

• The model Name value starts with an uppercase C (\"Cohere-command...\") while many other model names in this list use lowercase naming. If the downstream service treats model IDs as case-sensitive (common for identifiers), this could cause mismatches. Consider normalizing the casing to match the conventions used by the rest of the catalog.

FoundryModels.Cohere.CohereCommandAPlus052026: Aspire.Hosting.Foundry/Aspire.Hosting.Foundry.FoundryModel = {"Name":"Cohere-command-a-plus-05-2026","Version":"1","Format":"Cohere"}

[Copilot]

Pull request overview

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

Suppressed comments (1)

src/Aspire.Hosting.Kubernetes/api/Aspire.Hosting.Kubernetes.ats.txt:3

• The withPvCapacityParam / withPvStorageClassParam names are inconsistent with the non-parameter counterparts (withCapacity, withStorageClass), which typically follow the withXParam pattern. Consider renaming to withCapacityParam and withStorageClassParam (or a consistent project-wide convention) to reduce API discoverability friction.