[release/13.4] Validate playwrightCliVersion shape with strict SemVer#18205
Merged
joperezr merged 1 commit intoJun 16, 2026
Merged
Conversation
The playwrightCliVersion configuration value is forwarded to npm as the package version specifier. Previously any non-empty string would be passed through, so a typo or unsupported shape (a range, an npm dist-tag like 'latest', a v-prefixed version, etc.) would surface as a generic 'failed to resolve' error from npm. Validate the override with SemVersion.TryParse using SemVersionStyles.Strict and fail fast with a clear message that names the configuration key and the offending value when it is not a valid SemVer 2.0 version. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 18205Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 18205" |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds strict SemVer 2.0 validation for the playwrightCliVersion configuration override in the Playwright CLI installer. Previously, any string (including npm ranges like >=0.2.0, dist-tags like latest, or malformed values) could be passed through to npm. Now, the installer validates the override is a well-formed MAJOR.MINOR.PATCH version before forwarding it, returning a clear error message on failure.
Changes:
- Adds
SemVersion.TryParsevalidation withSemVersionStyles.Strictbefore accepting a version override, with an early-return failure path and descriptive error message. - Adds a localized resource string (
PlaywrightCliInstaller_InvalidVersionOverride) across the.resxand all 11.xlffiles. - Adds a
[Theory]test with 5 invalid version variants verifying the installer returnsFailedstatus without calling npm.
Show a summary per file
| File | Description |
|---|---|
| src/Aspire.Cli/Agents/Playwright/PlaywrightCliInstaller.cs | Adds strict SemVer validation guard before using the version override |
| tests/Aspire.Cli.Tests/Agents/PlaywrightCliInstallerTests.cs | Adds parameterized test covering invalid version override values |
| src/Aspire.Cli/Resources/AgentCommandStrings.resx | Adds new resource string for invalid version error |
| src/Aspire.Cli/Resources/AgentCommandStrings.Designer.cs | Auto-generated property for the new resource string |
| src/Aspire.Cli/Resources/xlf/AgentCommandStrings.*.xlf (11 files) | Localization entries for the new error message |
Copilot's findings
Files not reviewed (1)
- src/Aspire.Cli/Resources/AgentCommandStrings.Designer.cs: Generated file
- Files reviewed: 16/17 changed files
- Comments generated: 0
Contributor
|
❓ CLI E2E Tests unknown — 112 passed, 0 failed, 2 unknown (commit View all recordings
📹 Recordings uploaded automatically from CI run #27521770478 |
JamesNK
approved these changes
Jun 15, 2026
radical
changed the title
joperezr
deleted the
mitchdenny/validate-playwright-cli-version-release-13.4
branch
aspire-repo-bot Bot
added a commit
to microsoft/aspire.dev
that referenced
this pull request
Jun 16, 2026
Document the playwrightCliVersion configuration setting and its strict SemVer 2.0 requirement, introduced in microsoft/aspire#18205. The Playwright CLI installer now validates that playwrightCliVersion contains a MAJOR.MINOR.PATCH version string before forwarding it to npm. Dist-tags (latest), ranges (>=1.0.0), and v-prefixed forms (v1.52.0) are all rejected with a descriptive error message. Add a 'Pin the Playwright CLI version' section to aspire-skills.mdx covering the configuration key, valid format, and the new error message users may see if their config value does not pass validation. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Pull request created: #1265
|
Contributor
|
📝 Documentation has been drafted in microsoft/aspire.dev#1265 targeting Added a new "Pin the Playwright CLI version" section to Note This draft PR needs human review before merging. |
This was referenced Jun 17, 2026
This was referenced Jun 22, 2026
Open
rombolshak
pushed a commit
to rombolshak/ahlcg
that referenced
this pull request
Jun 23, 2026
Updated [Aspire.Hosting.JavaScript](https://github.com/microsoft/aspire) from 13.2.2 to 13.4.6. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.JavaScript's releases](https://github.com/microsoft/aspire/releases)._ ## 13.4.6 ## What's New in Aspire 13.4.6 Patch release for Aspire 13.4 fixing polyglot AppHost code generation binding when CLI and SDK versions diverge, resource service port collision in `--isolated` mode, and a MongoDB.Driver dependency update. ### 🐛 Fixes - 🔗 **Polyglot AppHost code generation silently failed when CLI and SDK versions diverged** — `Aspire.TypeSystem` used a floating strong-name `AssemblyVersion` that changed with every build. When the installed Aspire CLI was built at a different version than the AppHost's SDK, the CLR couldn't satisfy the strong-name bind and every code generator (TypeScript, Python, Java, Go, Rust) was silently dropped, surfacing as `No code generator found for language: <lang>`. The `AssemblyVersion` is now frozen at a stable constant so any compatible CLI/SDK pair on 13.4 binds successfully. Relates to #18110 and #17910. ([#18160](https://github.com/microsoft/aspire/pull/18160), `@sebastienros`) - 🔌 **Multiple AppHosts started with `--isolated` collided on the resource service port** — Both instances tried to bind to the same fixed port from `ASPIRE_RESOURCE_SERVICE_ENDPOINT_URL`, causing an "address already in use" error on the second instance. `DashboardServiceHost` now binds to port 0 on loopback when `RandomizePorts` is true (set by `--isolated`), letting the OS assign a unique port per instance. ([#18341](https://github.com/microsoft/aspire/pull/18341), `@JamesNK`) - 🍃 **MongoDB.Driver updated to 3.9.0** — Removes a wrongly pinned `SharpCompress` transitive dependency and uses the corrected `Snappier` transitive. Fixes #17981. ([#18279](https://github.com/microsoft/aspire/pull/18279), `@Falco20019`) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.4.6 ([#18343](https://github.com/microsoft/aspire/pull/18343)) --- _Full Changelog: [v13.4.5...v13.4.6](https://github.com/microsoft/aspire/compare/v13.4.5...v13.4.6)_ _Full commit: [87fe259e4fc244c599019a7b1304c85a1488f248](https://github.com/microsoft/aspire/commit/87fe259e4fc244c599019a7b1304c85a1488f248)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27855270514) · 131 AIC · ⌖ 13.5 AIC · ⊞ 37.4K <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.60, model: claude-sonnet-4.6, id: 27855270514, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27855270514 --> ## 13.4.5 ## What's New in Aspire 13.4.5 Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry. ### 🐛 Fixes - 🛡️ **Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory** — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use `MessagePackFormatter` or LZ4 — all StreamJsonRpc calls use `SystemTextJsonFormatter` over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the `Aspire.Hosting` package. ([#18204](https://github.com/microsoft/aspire/pull/18204), `@mitchdenny`) - 🎭 **`playwrightCliVersion` values that are not valid SemVer 2.0 now fail fast with a clear diagnostic** — Previously an invalid override (range expression, dist-tag like `latest`, or a `v`-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. ([#18205](https://github.com/microsoft/aspire/pull/18205), `@mitchdenny`) - 🤖 **CLI telemetry now detects and reports the calling coding agent** — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as `copilot-cli`. ([#18240](https://github.com/microsoft/aspire/pull/18240), `@damianedwards`) ### 🏷️ Housekeeping - 📄 Refreshed the `@microsoft/aspire-cli` npm package README to be TypeScript-only — updated examples to the current `ts-starter` template (`apphost.mts` / `aspire.mjs`), added a backing-services snippet showing `aspire add` for PostgreSQL and Redis, and documented `aspire dashboard run` as a standalone dashboard option. ([#18221](https://github.com/microsoft/aspire/pull/18221), `@adamint`) --- _Full Changelog: [v13.4.4...v13.4.5](https://github.com/microsoft/aspire/compare/v13.4.4...v13.4.5)_ _Full commit: [73114e86c64aeb9f3f3c7da8e37df1ae4281b27e](https://github.com/microsoft/aspire/commit/73114e86c64aeb9f3f3c7da8e37df1ae4281b27e)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27667814104/agentic_workflow) · ● 4.4M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 27667814104, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27667814104 --> ## 13.4.4 ## What's New in Aspire 13.4.4 Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent `ExcludeFromMcp()` filtering across all CLI MCP tools. ### 🐛 Fixes * 🔌 **DCP requests could fail permanently when the connection dropped mid-request** — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. ([#18096](https://github.com/microsoft/aspire/pull/18096), `@karolz-ms`) * 🔍 **Resources marked with `ExcludeFromMcp()` were not consistently filtered from CLI MCP tools** — Resources with the `resource.excludeFromMcp` property were not excluded uniformly from all CLI MCP tool results. `list_resources`, `list_console_logs`, `execute_resource_command`, `list_structured_logs`, `list_traces`, and `list_trace_structured_logs` all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. ([#18150](https://github.com/microsoft/aspire/pull/18150), `@JamesNK`) ### 🏷️ Housekeeping * 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. ([#18093](https://github.com/microsoft/aspire/pull/18093), `@adamratzman`) * * * _Full Changelog: [v13.4.3...v13.4.4](https://github.com/microsoft/aspire/compare/v13.4.3...v13.4.4)_ _Full commit: [ccc566c5ab3285c9beb8f38ede34734bb477c029](https://github.com/microsoft/aspire/commit/ccc566c5ab3285c9beb8f38ede34734bb477c029)_ ## 13.4.3 ## What's New in Aspire 13.4.3 Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4. ### 🐛 Fixes - 🔌 **Persistent container endpoints had incorrect default behavior** — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with `isProxied: false` or `WithEndpointProxySupport(false)`. Proxyless container endpoints with only a `targetPort` specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, `@danegsta`) ### 🏷️ Housekeeping - 🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.2...v13.4.3* *Full commit: [4f218933552e18ff2874d1b6d5dc3fe671e3b6d9](https://github.com/microsoft/aspire/commit/4f218933552e18ff2874d1b6d5dc3fe671e3b6d9)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27173824611/agentic_workflow) · ● 4.7M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 27173824611, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27173824611 --> ## 13.4.2 ## What's New in Aspire 13.4.2 Patch release for Aspire 13.4 with a fix for Redis persistent container deadlock on startup when using TLS. ### 🐛 Fixes - 🔴 **Redis with `WithLifetime(ContainerLifetime.Persistent)` could deadlock on startup** — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850, `@danegsta`) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.4.2 (#17876) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.1...v13.4.2* *Full commit: [d7d0b6759ce4b936c76bc4775814d27db560dd6d](https://github.com/microsoft/aspire/commit/d7d0b6759ce4b936c76bc4775814d27db560dd6d)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26920328099/agentic_workflow) · ● 5M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26920328099, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26920328099 --> ## 13.4.1 ## What's New in Aspire 13.4.1 Patch release for Aspire 13.4 with fixes for explicit-start resource lifecycle callbacks, Redis persistent container startup, proxyless endpoint allocation, and a duplicated `profiles` block in the empty C# AppHost template. ### 🐛 Fixes - ⏱️ **Explicit-start resources triggered lifecycle callbacks too early** — Session-scoped resources marked with `WithExplicitStart()` were having their execution configuration callbacks (environment variables, arguments, certificates) evaluated at AppHost startup instead of at manual start. This meant user-interaction callbacks such as `WithEnvironment(ctx => PromptForValueAsync(...))` were called before the user triggered the resource. DCP registration is now deferred until the user manually starts the resource; persistent explicit-start resources still register immediately but patch the existing DCP record to `Start = true` rather than deleting and recreating it. Fixes #17813. (#17825, backported via #17826, `@danegsta`) - 🔴 **Redis with `WithLifetime(ContainerLifetime.Persistent)` could deadlock on startup** — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850, `@danegsta`) - 🔌 **Proxyless container endpoint could hang when resolved before container creation** — Referencing a proxyless container endpoint in an environment variable callback (before the container port spec was finalized) could deadlock. An on-demand allocation path now commits the target port as the fallback host port in that case; once `BuildContainerPorts` runs, normal DCP dynamic port assignment takes over for any later resolution. (#17851, backported via #17859, `@danegsta`) - 📄 **Empty C# AppHost template emitted duplicate `profiles` block** — `aspire new aspire-empty` on 13.4 produced an `aspire.config.json` with a `profiles` block that duplicated the content already present in `apphost.run.json`, causing redundant launch configuration. The embedded template now contains only the required `appHost.path` binding; profile configuration lives exclusively in `apphost.run.json`. Fixes #17660. (#17781, backported via #17820, `@mitchdenny`) ### 🏷️ Housekeeping - 📦 Added Aspire CLI npm package to the release pipeline so the npm distribution is published as part of stable releases. (#17297, backported via #17766, `@adamint`) - 🚀 Bumped branding to 13.4.1 (#17819) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.0...v13.4.1* *Full commit: [cf985fa817dd5863e7f62eb74fa1725ab5069ed2](https://github.com/microsoft/aspire/commit/cf985fa817dd5863e7f62eb74fa1725ab5069ed2)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26909313891/agentic_workflow) · ● 1.0.40 > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26909313891/agentic_workflow) · ● 3.9M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26909313891, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26909313891 --> ## 13.4.0 # Aspire 13.4.0 Aspire 13.4 brings major improvements to Foundry hosted agents, the Aspire skills system, CLI reliability, and TypeScript AppHost stability — with cross-compute-environment deployment now working end-to-end and **TypeScript AppHost support — Aspire's polyglot story — reaching general availability (GA)**. ## Highlights - 🎉 **TypeScript AppHost is now GA** — First introduced as a preview in an earlier version of Aspire, the TypeScript AppHost — Aspire's polyglot story — has reached the quality bar for general availability and is now officially supported for production use alongside C#. As part of GA, the experimental markers on the Azure TypeScript AppHost (ATS) APIs have been removed and the ATS surface area is stable for 13.4. - 🤖 **Foundry hosted agents** — Protocol selection (`responses` / `invocations`) is now configurable from both C# and TypeScript AppHosts. Cross-compute-environment deployments (e.g., a Foundry hosted agent + an AKS consumer) now wire up correctly: endpoint resolution and the required **Azure AI User** RBAC role assignment on the Foundry account are generated automatically — no manual `az role assignment create` steps needed. - 🛠️ **Aspire skills catalog from bundle** — `aspire agent init` now drives its installable skill catalog from the bundle manifest, surfacing all six bundled skills (previously only three were visible). An embedded snapshot means the full catalog is available even in airgapped / disconnected environments. - 🔧 **CLI reliability** — Multiple CLI fixes: implicit-channel discovery restored, `aspire stop` no longer falsely reports failure on Unix, `aspire ps` no longer includes raw resource data (use `aspire describe` for detailed state), `aspire new` prefers the current CLI template version, friendly error for `aspire do --list-steps` without a step argument, and improved `--search` option description with documentation link. - ⌨️ **TypeScript AppHost** — Fixed a deadlock that occurred when lazy options callbacks invoked async methods; dev-localhost resource service URLs are now accepted for local development without extra configuration. - 📊 **Dashboard** — Summary log formatting improved for readability, `dotnet watch` dashboard auto-launch signal restored, and dynamic-port handling fixed for `DistributedApplicationTestingBuilder`. - ☸️ **Kubernetes** — The Helm CLI minimum version (≥ 4.2.0) is now validated before a Kubernetes deploy, giving a clear error instead of a cryptic failure. - ⚠️ **`Aspire.Hosting.Blazor` ships as preview in 13.4** — A packaging issue with the Blazor gateway scripts means the package is intentionally marked preview for this release. Full stable support is targeted for 13.5. ## ⚠️ Notable changes - `aspire ps` no longer includes raw resource data in its output. Use `aspire describe <resource>` to inspect detailed resource state. - Foundry hosted agent builder API shape updated — see [#17545](https://github.com/microsoft/aspire/pull/17545) and [#17669](https://github.com/microsoft/aspire/pull/17669) for the updated C# and TypeScript signatures. - `Aspire.Hosting.Blazor` is preview-versioned in 13.4 (`SuppressFinalPackageVersion=true`). A fix for the `addBlazorGateway` gateway script resolution error in TypeScript AppHosts is tracked in [#17685](https://github.com/microsoft/aspire/issues/17685). ## 📖 Learn more For the full details on everything in this release, check out the [What's new in Aspire 13.4](https://aspire.dev/whats-new/aspire-13-4/) documentation. Thank you to all the community contributors who helped make Aspire 13.4 possible! 💜 --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.3.5...v13.4.0* *Full commit: [becb48e2d61099e35ae336d527d3875e928d6594](https://github.com/microsoft/aspire/commit/becb48e2d61099e35ae336d527d3875e928d6594)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26779980139/agentic_workflow) · ● 6.5M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26779980139, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26779980139 --> ## 13.3.5 ## What's New in Aspire 13.3.5 Patch release for Aspire 13.3 with fixes for the Azure provisioning location prompt and an Aspire CLI named-pipe timeout on Linux with .NET SDK 10.0.300. ### 🐛 Fixes - 📍 **Azure provisioning location prompt not populated** — Selecting an existing resource group during `aspire publish` now correctly populates dependent server-controlled fields (such as Location). Previously, server-provided values for disabled inputs were discarded, leaving those fields blank. (#17278, backported via #17291) - 🔧 **Aspire CLI named-pipe timeout on Linux with .NET SDK 10.0.300** — The Aspire CLI was forcing `DOTNET_CLI_USE_MSBUILD_SERVER=1` for all `dotnet run`/`dotnet build` invocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that prevented `aspire run` from building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314) ### 🏷️ Housekeeping - ⬆️ Skipped log publish for WinGet/Homebrew installer pipeline jobs to fix Prepare Installers stage failures (#17134) - 🚀 Bumped branding to 13.3.5 (#17315) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.3.4...v13.3.5* *Full commit: [70b33bcb5f64c75e3ab6f57616545f35bd43dc81](https://github.com/microsoft/aspire/commit/70b33bcb5f64c75e3ab6f57616545f35bd43dc81)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26241645258/agentic_workflow) · ● 4.3M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26241645258, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26241645258 --> ## 13.3.4 ## What's New in Aspire 13.3.4 Patch release for Aspire 13.3 with a fix for the Aspire skill description exceeding agent host limits. ### 🐛 Fixes - 📝 **Aspire skill description too long for agent hosts** — The `SKILL.md` generated by `aspire agent init` included a frontmatter description that exceeded the 1024-character limit enforced by agent hosts such as Codex and Copilot CLI, causing the Aspire skill to fail to load. The bundled skill description has been shortened to stay within the limit. (#17183, backported via #17188) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.3.4 (#17215) --- *Full commit: [75080796af797483231a9da2d1642b5130617565](https://github.com/microsoft/aspire/commit/75080796af797483231a9da2d1642b5130617565)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26123829267/agentic_workflow) · ● 3.6M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26123829267, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26123829267 --> ## 13.3.3 ## What's New in Aspire 13.3.3 Patch release for Aspire 13.3 with fixes for debug log level leaking into user resources, Keycloak HTTPS endpoint token invalidation, and endpoint materialization in `HostResourceWithEndpoints`. ### 🐛 Fixes - 🔇 **Debug log level leaking into user resources** — `Logging__LogLevel__Default=Debug` set by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now uses `ASPIRE_APPHOST_LOGLEVEL` instead, which is scoped to Aspire processes only. (#17071, backported via #17078) - 🔑 **Keycloak HTTPS primary endpoint** — Fixed a regression where Keycloak tokens became invalid after an app host restart because the HTTPS endpoint port was dynamic. When developer certificates are enabled, Keycloak's primary endpoint is now upgraded to HTTPS directly, and the endpoint name is set to `http` to enable standard `http+https://` service discovery URLs. (#17058, backported via #17063) - 🔌 **Endpoint materialization in `HostResourceWithEndpoints`** — Endpoints configured via `HostResourceWithEndpoints` are now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092) ### 🏷️ Housekeeping - ⬆️ Bumped DCP (Microsoft.DeveloperControlPlane) from 0.23.5 → 0.23.6 — includes fixes for Kubernetes OpenAPI generator types that caused `[SHOULD NOT HAPPEN] failed to update managedFields` errors. (#17070) - 🚀 Bumped branding to 13.3.3 (#17088) --- *Full commit: [a4615e7c6def6cba4703cdbd84009cd3da9a261b](https://github.com/microsoft/aspire/commit/a4615e7c6def6cba4703cdbd84009cd3da9a261b)* ## 13.3.2 ## What's New in Aspire 13.3.2 Patch release for Aspire 13.3 with a fix for container tunnel startup when tunnel-dependent containers use `WaitFor()`. ### 🐛 Fixes - 🚇 Fix `WaitFor()` for tunnel-dependent containers — The container tunnel implementation that shipped in Aspire 13.3 deadlocked at startup when tunnel-using containers waited on other resources, because resource waits blocked `ResourceStarting` before the tunnel initialization could complete. Container and tunnel startup have been refactored to cooperate correctly, and additional tunnel-dependent containers can now be started at any point during the application lifecycle. Also improves error reporting for container tunnel failures. (#16988, backported via #16993) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.3.2 (#17053) ## 13.3.1 # Aspire 13.3.1 ## What's New in Aspire 13.3.1 Patch release for Aspire 13.3 with a regression fix for `aspire run` and a DCP bump. ### 🐛 Fixes - 🏃 **`aspire run` compute environment validation** — Skip compute environment validation in run mode so customers no longer hit `Resource '<name>' is configured to publish as an Azure Container App, but there are no 'AzureContainerAppEnvironmentResource' resources. Ensure you have added one by calling 'AddAzureContainerAppEnvironment'.` errors during local runs. The check is now only performed in publish mode, matching pre-13.3 behavior. (#16945, backported via #16952) ### 🏷️ Housekeeping - ⬆️ Bumped DCP (Microsoft.DeveloperControlPlane) from 0.23.4 → 0.23.5 (#16944) - 🌐 Updated localization resources (#16602) - 🚀 Bumped branding to 13.3.1 (#16951) ## 13.3.0 # Aspire 13.3.0 Aspire 13.3 is here! 🚀 This release is packed with new ways to deploy, debug, and build distributed apps — including `aspire destroy`, browser telemetry in the dashboard, Kubernetes deployment, first-class JavaScript publishing, and major TypeScript AppHost parity improvements. ## Highlights - 🧹 **Clean teardown** — New **`aspire destroy`** tears down Azure, Kubernetes, and Docker Compose deployments, and pipeline summaries make deploy/publish/destroy runs easier to follow. - 🔍 **Frontend telemetry** — **Aspire.Hosting.Browsers** captures browser console logs, network requests, and screenshots right in the Aspire dashboard. - ☸️ **Kubernetes deploy preview** — **`aspire deploy`** can now generate Helm-based Kubernetes deployments, with first-class Ingress and Gateway API routing. - 🟨 **JavaScript publishing** — New **`PublishAs*`** methods support static sites, Node servers, npm-script apps, Next.js, Vite, Bun, Yarn, and pnpm. - 🌐 **TypeScript AppHost parity** — Unified `withEnvironment`, Docker Compose hooks, endpoint expressions, Azure Container Apps domains, and more close the gap with C# AppHosts. - 🛠️ **CLI upgrades** — Run the standalone dashboard with **`aspire dashboard run`**, install the CLI as a NativeAOT `dotnet tool`, and search API docs from the terminal. - ☁️ **Azure goodness** — New Azure Front Door, Network Security Perimeter, AKS, private endpoint, and Foundry Prompt Agent support. - 🐳 **Better containers** — The Aspire container tunnel is now enabled by default for consistent host connectivity across Docker Desktop, Docker Engine, and Podman. ## ⚠️ Breaking changes Notable breaking changes include `--log-level` becoming `--pipeline-log-level`, the dashboard MCP server being replaced by `aspire agent init`, `dotnet new aspire-py-starter` moving to `aspire new aspire-py-starter`, and several API shape updates across AKS, Foundry, JavaScript diagnostics, and TypeScript AppHost helpers. See the full list in the [Aspire 13.3 breaking changes](https://aspire.dev/whats-new/aspire-13-3/#%EF%B8%8F-breaking-changes). ## 📖 Learn more For the full details, examples, migration guidance, and everything new in this release, check out [What's new in Aspire 13.3](https://aspire.dev/whats-new/aspire-13-3/). Thank you to all the community contributors who helped make Aspire 13.3 possible! 💜 ## 13.2.4 # Aspire 13.2.4 ## What's New in Aspire 13.2.4 Patch release addressing a security advisory in OpenTelemetry dependencies. ### 🐛 Fixes - 🔒 Bumped OpenTelemetry dependencies to address CVE-2026-40894 (#16420) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.2.4 (#16436) ## 13.2.3 # What's New in Aspire 13.2.3 Patch release focused on CLI packaging, signing, and reliability fixes. ## 🐛 Fixes - 🛑 aspire stop now properly cleans up application containers on Windows (#16123) - 🔐 Fixed macOS signing, permissions, and certificate trust with improved CI verification (#16053) - ✍️ Fixed signing for the aspire-managed bundle payload (#16211) - 🎭 Fixed Playwright CLI provenance verification for the new tag format (#16134) - 🧭 Updated service discovery environment variables (#16223) ## 🔧 Improvements - 📊 Removed telemetry API data limits and refactored URL builders (#16023) - ⏱️ Increased native build + sign timeout to 60 minutes for reliability (#16212) ## 🏷️ Housekeeping - 🔖 Bumped branding to 13.2.3 (#16181) - 🧪 Temporarily disabled Verify CLI archive step on Windows while investigating (#16276, #16285) Commits viewable in [compare view](https://github.com/microsoft/aspire/compare/v13.2.2...v13.4.6). </details> Updated [Aspire.Hosting.PostgreSQL](https://github.com/microsoft/aspire) from 13.2.2 to 13.4.6. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.PostgreSQL's releases](https://github.com/microsoft/aspire/releases)._ ## 13.4.6 ## What's New in Aspire 13.4.6 Patch release for Aspire 13.4 fixing polyglot AppHost code generation binding when CLI and SDK versions diverge, resource service port collision in `--isolated` mode, and a MongoDB.Driver dependency update. ### 🐛 Fixes - 🔗 **Polyglot AppHost code generation silently failed when CLI and SDK versions diverged** — `Aspire.TypeSystem` used a floating strong-name `AssemblyVersion` that changed with every build. When the installed Aspire CLI was built at a different version than the AppHost's SDK, the CLR couldn't satisfy the strong-name bind and every code generator (TypeScript, Python, Java, Go, Rust) was silently dropped, surfacing as `No code generator found for language: <lang>`. The `AssemblyVersion` is now frozen at a stable constant so any compatible CLI/SDK pair on 13.4 binds successfully. Relates to #18110 and #17910. ([#18160](https://github.com/microsoft/aspire/pull/18160), `@sebastienros`) - 🔌 **Multiple AppHosts started with `--isolated` collided on the resource service port** — Both instances tried to bind to the same fixed port from `ASPIRE_RESOURCE_SERVICE_ENDPOINT_URL`, causing an "address already in use" error on the second instance. `DashboardServiceHost` now binds to port 0 on loopback when `RandomizePorts` is true (set by `--isolated`), letting the OS assign a unique port per instance. ([#18341](https://github.com/microsoft/aspire/pull/18341), `@JamesNK`) - 🍃 **MongoDB.Driver updated to 3.9.0** — Removes a wrongly pinned `SharpCompress` transitive dependency and uses the corrected `Snappier` transitive. Fixes #17981. ([#18279](https://github.com/microsoft/aspire/pull/18279), `@Falco20019`) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.4.6 ([#18343](https://github.com/microsoft/aspire/pull/18343)) --- _Full Changelog: [v13.4.5...v13.4.6](https://github.com/microsoft/aspire/compare/v13.4.5...v13.4.6)_ _Full commit: [87fe259e4fc244c599019a7b1304c85a1488f248](https://github.com/microsoft/aspire/commit/87fe259e4fc244c599019a7b1304c85a1488f248)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27855270514) · 131 AIC · ⌖ 13.5 AIC · ⊞ 37.4K <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.60, model: claude-sonnet-4.6, id: 27855270514, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27855270514 --> ## 13.4.5 ## What's New in Aspire 13.4.5 Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry. ### 🐛 Fixes - 🛡️ **Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory** — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use `MessagePackFormatter` or LZ4 — all StreamJsonRpc calls use `SystemTextJsonFormatter` over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the `Aspire.Hosting` package. ([#18204](https://github.com/microsoft/aspire/pull/18204), `@mitchdenny`) - 🎭 **`playwrightCliVersion` values that are not valid SemVer 2.0 now fail fast with a clear diagnostic** — Previously an invalid override (range expression, dist-tag like `latest`, or a `v`-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. ([#18205](https://github.com/microsoft/aspire/pull/18205), `@mitchdenny`) - 🤖 **CLI telemetry now detects and reports the calling coding agent** — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as `copilot-cli`. ([#18240](https://github.com/microsoft/aspire/pull/18240), `@damianedwards`) ### 🏷️ Housekeeping - 📄 Refreshed the `@microsoft/aspire-cli` npm package README to be TypeScript-only — updated examples to the current `ts-starter` template (`apphost.mts` / `aspire.mjs`), added a backing-services snippet showing `aspire add` for PostgreSQL and Redis, and documented `aspire dashboard run` as a standalone dashboard option. ([#18221](https://github.com/microsoft/aspire/pull/18221), `@adamint`) --- _Full Changelog: [v13.4.4...v13.4.5](https://github.com/microsoft/aspire/compare/v13.4.4...v13.4.5)_ _Full commit: [73114e86c64aeb9f3f3c7da8e37df1ae4281b27e](https://github.com/microsoft/aspire/commit/73114e86c64aeb9f3f3c7da8e37df1ae4281b27e)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27667814104/agentic_workflow) · ● 4.4M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 27667814104, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27667814104 --> ## 13.4.4 ## What's New in Aspire 13.4.4 Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent `ExcludeFromMcp()` filtering across all CLI MCP tools. ### 🐛 Fixes * 🔌 **DCP requests could fail permanently when the connection dropped mid-request** — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. ([#18096](https://github.com/microsoft/aspire/pull/18096), `@karolz-ms`) * 🔍 **Resources marked with `ExcludeFromMcp()` were not consistently filtered from CLI MCP tools** — Resources with the `resource.excludeFromMcp` property were not excluded uniformly from all CLI MCP tool results. `list_resources`, `list_console_logs`, `execute_resource_command`, `list_structured_logs`, `list_traces`, and `list_trace_structured_logs` all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. ([#18150](https://github.com/microsoft/aspire/pull/18150), `@JamesNK`) ### 🏷️ Housekeeping * 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. ([#18093](https://github.com/microsoft/aspire/pull/18093), `@adamratzman`) * * * _Full Changelog: [v13.4.3...v13.4.4](https://github.com/microsoft/aspire/compare/v13.4.3...v13.4.4)_ _Full commit: [ccc566c5ab3285c9beb8f38ede34734bb477c029](https://github.com/microsoft/aspire/commit/ccc566c5ab3285c9beb8f38ede34734bb477c029)_ ## 13.4.3 ## What's New in Aspire 13.4.3 Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4. ### 🐛 Fixes - 🔌 **Persistent container endpoints had incorrect default behavior** — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with `isProxied: false` or `WithEndpointProxySupport(false)`. Proxyless container endpoints with only a `targetPort` specified now also resolve immediately to that port instead of waiting for delayed allocation. (#17960, `@danegsta`) ### 🏷️ Housekeeping - 🛠️ Unblocked WinGet manifest publishing on locked-down 1ES agents and updated manifest tags (#17958) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.2...v13.4.3* *Full commit: [4f218933552e18ff2874d1b6d5dc3fe671e3b6d9](https://github.com/microsoft/aspire/commit/4f218933552e18ff2874d1b6d5dc3fe671e3b6d9)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27173824611/agentic_workflow) · ● 4.7M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 27173824611, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27173824611 --> ## 13.4.2 ## What's New in Aspire 13.4.2 Patch release for Aspire 13.4 with a fix for Redis persistent container deadlock on startup when using TLS. ### 🐛 Fixes - 🔴 **Redis with `WithLifetime(ContainerLifetime.Persistent)` could deadlock on startup** — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850, `@danegsta`) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.4.2 (#17876) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.1...v13.4.2* *Full commit: [d7d0b6759ce4b936c76bc4775814d27db560dd6d](https://github.com/microsoft/aspire/commit/d7d0b6759ce4b936c76bc4775814d27db560dd6d)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26920328099/agentic_workflow) · ● 5M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26920328099, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26920328099 --> ## 13.4.1 ## What's New in Aspire 13.4.1 Patch release for Aspire 13.4 with fixes for explicit-start resource lifecycle callbacks, Redis persistent container startup, proxyless endpoint allocation, and a duplicated `profiles` block in the empty C# AppHost template. ### 🐛 Fixes - ⏱️ **Explicit-start resources triggered lifecycle callbacks too early** — Session-scoped resources marked with `WithExplicitStart()` were having their execution configuration callbacks (environment variables, arguments, certificates) evaluated at AppHost startup instead of at manual start. This meant user-interaction callbacks such as `WithEnvironment(ctx => PromptForValueAsync(...))` were called before the user triggered the resource. DCP registration is now deferred until the user manually starts the resource; persistent explicit-start resources still register immediately but patch the existing DCP record to `Start = true` rather than deleting and recreating it. Fixes #17813. (#17825, backported via #17826, `@danegsta`) - 🔴 **Redis with `WithLifetime(ContainerLifetime.Persistent)` could deadlock on startup** — Redis TLS startup arguments used the public/allocated host ports instead of the internal target ports. When the public port differed from the target port (or was not yet allocated) the container would listen on an unexpected port and become unreachable. The TLS and non-TLS startup arguments now bind to target ports, matching what Redis expects internally. Fixes #17822. (#17827, backported via #17850, `@danegsta`) - 🔌 **Proxyless container endpoint could hang when resolved before container creation** — Referencing a proxyless container endpoint in an environment variable callback (before the container port spec was finalized) could deadlock. An on-demand allocation path now commits the target port as the fallback host port in that case; once `BuildContainerPorts` runs, normal DCP dynamic port assignment takes over for any later resolution. (#17851, backported via #17859, `@danegsta`) - 📄 **Empty C# AppHost template emitted duplicate `profiles` block** — `aspire new aspire-empty` on 13.4 produced an `aspire.config.json` with a `profiles` block that duplicated the content already present in `apphost.run.json`, causing redundant launch configuration. The embedded template now contains only the required `appHost.path` binding; profile configuration lives exclusively in `apphost.run.json`. Fixes #17660. (#17781, backported via #17820, `@mitchdenny`) ### 🏷️ Housekeeping - 📦 Added Aspire CLI npm package to the release pipeline so the npm distribution is published as part of stable releases. (#17297, backported via #17766, `@adamint`) - 🚀 Bumped branding to 13.4.1 (#17819) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.4.0...v13.4.1* *Full commit: [cf985fa817dd5863e7f62eb74fa1725ab5069ed2](https://github.com/microsoft/aspire/commit/cf985fa817dd5863e7f62eb74fa1725ab5069ed2)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26909313891/agentic_workflow) · ● 1.0.40 > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26909313891/agentic_workflow) · ● 3.9M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26909313891, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26909313891 --> ## 13.4.0 # Aspire 13.4.0 Aspire 13.4 brings major improvements to Foundry hosted agents, the Aspire skills system, CLI reliability, and TypeScript AppHost stability — with cross-compute-environment deployment now working end-to-end and **TypeScript AppHost support — Aspire's polyglot story — reaching general availability (GA)**. ## Highlights - 🎉 **TypeScript AppHost is now GA** — First introduced as a preview in an earlier version of Aspire, the TypeScript AppHost — Aspire's polyglot story — has reached the quality bar for general availability and is now officially supported for production use alongside C#. As part of GA, the experimental markers on the Azure TypeScript AppHost (ATS) APIs have been removed and the ATS surface area is stable for 13.4. - 🤖 **Foundry hosted agents** — Protocol selection (`responses` / `invocations`) is now configurable from both C# and TypeScript AppHosts. Cross-compute-environment deployments (e.g., a Foundry hosted agent + an AKS consumer) now wire up correctly: endpoint resolution and the required **Azure AI User** RBAC role assignment on the Foundry account are generated automatically — no manual `az role assignment create` steps needed. - 🛠️ **Aspire skills catalog from bundle** — `aspire agent init` now drives its installable skill catalog from the bundle manifest, surfacing all six bundled skills (previously only three were visible). An embedded snapshot means the full catalog is available even in airgapped / disconnected environments. - 🔧 **CLI reliability** — Multiple CLI fixes: implicit-channel discovery restored, `aspire stop` no longer falsely reports failure on Unix, `aspire ps` no longer includes raw resource data (use `aspire describe` for detailed state), `aspire new` prefers the current CLI template version, friendly error for `aspire do --list-steps` without a step argument, and improved `--search` option description with documentation link. - ⌨️ **TypeScript AppHost** — Fixed a deadlock that occurred when lazy options callbacks invoked async methods; dev-localhost resource service URLs are now accepted for local development without extra configuration. - 📊 **Dashboard** — Summary log formatting improved for readability, `dotnet watch` dashboard auto-launch signal restored, and dynamic-port handling fixed for `DistributedApplicationTestingBuilder`. - ☸️ **Kubernetes** — The Helm CLI minimum version (≥ 4.2.0) is now validated before a Kubernetes deploy, giving a clear error instead of a cryptic failure. - ⚠️ **`Aspire.Hosting.Blazor` ships as preview in 13.4** — A packaging issue with the Blazor gateway scripts means the package is intentionally marked preview for this release. Full stable support is targeted for 13.5. ## ⚠️ Notable changes - `aspire ps` no longer includes raw resource data in its output. Use `aspire describe <resource>` to inspect detailed resource state. - Foundry hosted agent builder API shape updated — see [#17545](https://github.com/microsoft/aspire/pull/17545) and [#17669](https://github.com/microsoft/aspire/pull/17669) for the updated C# and TypeScript signatures. - `Aspire.Hosting.Blazor` is preview-versioned in 13.4 (`SuppressFinalPackageVersion=true`). A fix for the `addBlazorGateway` gateway script resolution error in TypeScript AppHosts is tracked in [#17685](https://github.com/microsoft/aspire/issues/17685). ## 📖 Learn more For the full details on everything in this release, check out the [What's new in Aspire 13.4](https://aspire.dev/whats-new/aspire-13-4/) documentation. Thank you to all the community contributors who helped make Aspire 13.4 possible! 💜 --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.3.5...v13.4.0* *Full commit: [becb48e2d61099e35ae336d527d3875e928d6594](https://github.com/microsoft/aspire/commit/becb48e2d61099e35ae336d527d3875e928d6594)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26779980139/agentic_workflow) · ● 6.5M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26779980139, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26779980139 --> ## 13.3.5 ## What's New in Aspire 13.3.5 Patch release for Aspire 13.3 with fixes for the Azure provisioning location prompt and an Aspire CLI named-pipe timeout on Linux with .NET SDK 10.0.300. ### 🐛 Fixes - 📍 **Azure provisioning location prompt not populated** — Selecting an existing resource group during `aspire publish` now correctly populates dependent server-controlled fields (such as Location). Previously, server-provided values for disabled inputs were discarded, leaving those fields blank. (#17278, backported via #17291) - 🔧 **Aspire CLI named-pipe timeout on Linux with .NET SDK 10.0.300** — The Aspire CLI was forcing `DOTNET_CLI_USE_MSBUILD_SERVER=1` for all `dotnet run`/`dotnet build` invocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that prevented `aspire run` from building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314) ### 🏷️ Housekeeping - ⬆️ Skipped log publish for WinGet/Homebrew installer pipeline jobs to fix Prepare Installers stage failures (#17134) - 🚀 Bumped branding to 13.3.5 (#17315) --- *Full Changelog: https://github.com/microsoft/aspire/compare/v13.3.4...v13.3.5* *Full commit: [70b33bcb5f64c75e3ab6f57616545f35bd43dc81](https://github.com/microsoft/aspire/commit/70b33bcb5f64c75e3ab6f57616545f35bd43dc81)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26241645258/agentic_workflow) · ● 4.3M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26241645258, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26241645258 --> ## 13.3.4 ## What's New in Aspire 13.3.4 Patch release for Aspire 13.3 with a fix for the Aspire skill description exceeding agent host limits. ### 🐛 Fixes - 📝 **Aspire skill description too long for agent hosts** — The `SKILL.md` generated by `aspire agent init` included a frontmatter description that exceeded the 1024-character limit enforced by agent hosts such as Codex and Copilot CLI, causing the Aspire skill to fail to load. The bundled skill description has been shortened to stay within the limit. (#17183, backported via #17188) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.3.4 (#17215) --- *Full commit: [75080796af797483231a9da2d1642b5130617565](https://github.com/microsoft/aspire/commit/75080796af797483231a9da2d1642b5130617565)* > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/26123829267/agentic_workflow) · ● 3.6M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 26123829267, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/26123829267 --> ## 13.3.3 ## What's New in Aspire 13.3.3 Patch release for Aspire 13.3 with fixes for debug log level leaking into user resources, Keycloak HTTPS endpoint token invalidation, and endpoint materialization in `HostResourceWithEndpoints`. ### 🐛 Fixes - 🔇 **Debug log level leaking into user resources** — `Logging__LogLevel__Default=Debug` set by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now uses `ASPIRE_APPHOST_LOGLEVEL` instead, which is scoped to Aspire processes only. (#17071, backported via #17078) - 🔑 **Keycloak HTTPS primary endpoint** — Fixed a regression where Keycloak tokens became invalid after an app host restart because the HTTPS endpoint port was dynamic. When developer certificates are enabled, Keycloak's primary endpoint is now upgraded to HTTPS directly, and the endpoint name is set to `http` to enable standard `http+https://` service discovery URLs. (#17058, backported via #17063) - 🔌 **Endpoint materialization in `HostResourceWithEndpoints`** — Endpoints configured via `HostResourceWithEndpoints` are now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092) ### 🏷️ Housekeeping - ⬆️ Bumped DCP (Microsoft.DeveloperControlPlane) from 0.23.5 → 0.23.6 — includes fixes for Kubernetes OpenAPI generator types that caused `[SHOULD NOT HAPPEN] failed to update managedFields` errors. (#17070) - 🚀 Bumped branding to 13.3.3 (#17088) --- *Full commit: [a4615e7c6def6cba4703cdbd84009cd3da9a261b](https://github.com/microsoft/aspire/commit/a4615e7c6def6cba4703cdbd84009cd3da9a261b)* ## 13.3.2 ## What's New in Aspire 13.3.2 Patch release for Aspire 13.3 with a fix for container tunnel startup when tunnel-dependent containers use `WaitFor()`. ### 🐛 Fixes - 🚇 Fix `WaitFor()` for tunnel-dependent containers — The container tunnel implementation that shipped in Aspire 13.3 deadlocked at startup when tunnel-using containers waited on other resources, because resource waits blocked `ResourceStarting` before the tunnel initialization could complete. Container and tunnel startup have been refactored to cooperate correctly, and additional tunnel-dependent containers can now be started at any point during the application lifecycle. Also improves error reporting for container tunnel failures. (#16988, backported via #16993) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.3.2 (#17053) ## 13.3.1 # Aspire 13.3.1 ## What's New in Aspire 13.3.1 Patch release for Aspire 13.3 with a regression fix for `aspire run` and a DCP bump. ### 🐛 Fixes - 🏃 **`aspire run` compute environment validation** — Skip compute environment validation in run mode so customers no longer hit `Resource '<name>' is configured to publish as an Azure Container App, but there are no 'AzureContainerAppEnvironmentResource' resources. Ensure you have added one by calling 'AddAzureContainerAppEnvironment'.` errors during local runs. The check is now only performed in publish mode, matching pre-13.3 behavior. (#16945, backported via #16952) ### 🏷️ Housekeeping - ⬆️ Bumped DCP (Microsoft.DeveloperControlPlane) from 0.23.4 → 0.23.5 (#16944) - 🌐 Updated localization resources (#16602) - 🚀 Bumped branding to 13.3.1 (#16951) ## 13.3.0 # Aspire 13.3.0 Aspire 13.3 is here! 🚀 This release is packed with new ways to deploy, debug, and build distributed apps — including `aspire destroy`, browser telemetry in the dashboard, Kubernetes deployment, first-class JavaScript publishing, and major TypeScript AppHost parity improvements. ## Highlights - 🧹 **Clean teardown** — New **`aspire destroy`** tears down Azure, Kubernetes, and Docker Compose deployments, and pipeline summaries make deploy/publish/destroy runs easier to follow. - 🔍 **Frontend telemetry** — **Aspire.Hosting.Browsers** captures browser console logs, network requests, and screenshots right in the Aspire dashboard. - ☸️ **Kubernetes deploy preview** — **`aspire deploy`** can now generate Helm-based Kubernetes deployments, with first-class Ingress and Gateway API routing. - 🟨 **JavaScript publishing** — New **`PublishAs*`** methods support static sites, Node servers, npm-script apps, Next.js, Vite, Bun, Yarn, and pnpm. - 🌐 **TypeScript AppHost parity** — Unified `withEnvironment`, Docker Compose hooks, endpoint expressions, Azure Container Apps domains, and more close the gap with C# AppHosts. - 🛠️ **CLI upgrades** — Run the standalone dashboard with **`aspire dashboard run`**, install the CLI as a NativeAOT `dotnet tool`, and search API docs from the terminal. - ☁️ **Azure goodness** — New Azure Front Door, Network Security Perimeter, AKS, private endpoint, and Foundry Prompt Agent support. - 🐳 **Better containers** — The Aspire container tunnel is now enabled by default for consistent host connectivity across Docker Desktop, Docker Engine, and Podman. ## ⚠️ Breaking changes Notable breaking changes include `--log-level` becoming `--pipeline-log-level`, the dashboard MCP server being replaced by `aspire agent init`, `dotnet new aspire-py-starter` moving to `aspire new aspire-py-starter`, and several API shape updates across AKS, Foundry, JavaScript diagnostics, and TypeScript AppHost helpers. See the full list in the [Aspire 13.3 breaking changes](https://aspire.dev/whats-new/aspire-13-3/#%EF%B8%8F-breaking-changes). ## 📖 Learn more For the full details, examples, migration guidance, and everything new in this release, check out [What's new in Aspire 13.3](https://aspire.dev/whats-new/aspire-13-3/). Thank you to all the community contributors who helped make Aspire 13.3 possible! 💜 ## 13.2.4 # Aspire 13.2.4 ## What's New in Aspire 13.2.4 Patch release addressing a security advisory in OpenTelemetry dependencies. ### 🐛 Fixes - 🔒 Bumped OpenTelemetry dependencies to address CVE-2026-40894 (#16420) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.2.4 (#16436) ## 13.2.3 # What's New in Aspire 13.2.3 Patch release focused on CLI packaging, signing, and reliability fixes. ## 🐛 Fixes - 🛑 aspire stop now properly cleans up application containers on Windows (#16123) - 🔐 Fixed macOS signing, permissions, and certificate trust with improved CI verification (#16053) - ✍️ Fixed signing for the aspire-managed bundle payload (#16211) - 🎭 Fixed Playwright CLI provenance verification for the new tag format (#16134) - 🧭 Updated service discovery environment variables (#16223) ## 🔧 Improvements - 📊 Removed telemetry API data limits and refactored URL builders (#16023) - ⏱️ Increased native build + sign timeout to 60 minutes for reliability (#16212) ## 🏷️ Housekeeping - 🔖 Bumped branding to 13.2.3 (#16181) - 🧪 Temporarily disabled Verify CLI archive step on Windows while investigating (#16276, #16285) Commits viewable in [compare view](https://github.com/microsoft/aspire/compare/v13.2.2...v13.4.6). </details> Updated [Aspire.Npgsql.EntityFrameworkCore.PostgreSQL](https://github.com/microsoft/aspire) from 13.2.2 to 13.4.6. <details> <summary>Release notes</summary> _Sourced from [Aspire.Npgsql.EntityFrameworkCore.PostgreSQL's releases](https://github.com/microsoft/aspire/releases)._ ## 13.4.6 ## What's New in Aspire 13.4.6 Patch release for Aspire 13.4 fixing polyglot AppHost code generation binding when CLI and SDK versions diverge, resource service port collision in `--isolated` mode, and a MongoDB.Driver dependency update. ### 🐛 Fixes - 🔗 **Polyglot AppHost code generation silently failed when CLI and SDK versions diverged** — `Aspire.TypeSystem` used a floating strong-name `AssemblyVersion` that changed with every build. When the installed Aspire CLI was built at a different version than the AppHost's SDK, the CLR couldn't satisfy the strong-name bind and every code generator (TypeScript, Python, Java, Go, Rust) was silently dropped, surfacing as `No code generator found for language: <lang>`. The `AssemblyVersion` is now frozen at a stable constant so any compatible CLI/SDK pair on 13.4 binds successfully. Relates to #18110 and #17910. ([#18160](https://github.com/microsoft/aspire/pull/18160), `@sebastienros`) - 🔌 **Multiple AppHosts started with `--isolated` collided on the resource service port** — Both instances tried to bind to the same fixed port from `ASPIRE_RESOURCE_SERVICE_ENDPOINT_URL`, causing an "address already in use" error on the second instance. `DashboardServiceHost` now binds to port 0 on loopback when `RandomizePorts` is true (set by `--isolated`), letting the OS assign a unique port per instance. ([#18341](https://github.com/microsoft/aspire/pull/18341), `@JamesNK`) - 🍃 **MongoDB.Driver updated to 3.9.0** — Removes a wrongly pinned `SharpCompress` transitive dependency and uses the corrected `Snappier` transitive. Fixes #17981. ([#18279](https://github.com/microsoft/aspire/pull/18279), `@Falco20019`) ### 🏷️ Housekeeping - 🚀 Bumped branding to 13.4.6 ([#18343](https://github.com/microsoft/aspire/pull/18343)) --- _Full Changelog: [v13.4.5...v13.4.6](https://github.com/microsoft/aspire/compare/v13.4.5...v13.4.6)_ _Full commit: [87fe259e4fc244c599019a7b1304c85a1488f248](https://github.com/microsoft/aspire/commit/87fe259e4fc244c599019a7b1304c85a1488f248)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27855270514) · 131 AIC · ⌖ 13.5 AIC · ⊞ 37.4K <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.60, model: claude-sonnet-4.6, id: 27855270514, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27855270514 --> ## 13.4.5 ## What's New in Aspire 13.4.5 Patch release for Aspire 13.4 clearing a transitive MessagePack security advisory, tightening CLI validation for Playwright configuration, and adding coding-agent detection to CLI telemetry. ### 🐛 Fixes - 🛡️ **Bumped StreamJsonRpc to 2.25.29 to clear the MessagePack GHSA-hv8m-jj95-wg3x (CVE-2026-48109) NU1903 advisory** — The transitive MessagePack 2.5.192 dependency pulled in via StreamJsonRpc 2.22.23 fell within the advisory's vulnerable LZ4 decompression range. Aspire does not use `MessagePackFormatter` or LZ4 — all StreamJsonRpc calls use `SystemTextJsonFormatter` over local Unix sockets — so the vulnerability was not reachable in practice. The bump clears the NU1903 warning for consumers of the `Aspire.Hosting` package. ([#18204](https://github.com/microsoft/aspire/pull/18204), `@mitchdenny`) - 🎭 **`playwrightCliVersion` values that are not valid SemVer 2.0 now fail fast with a clear diagnostic** — Previously an invalid override (range expression, dist-tag like `latest`, or a `v`-prefixed string) would surface as a generic npm resolution failure. The value is now validated with strict SemVer parsing at startup; an error naming the configuration key and the offending value is emitted immediately. ([#18205](https://github.com/microsoft/aspire/pull/18205), `@mitchdenny`) - 🤖 **CLI telemetry now detects and reports the calling coding agent** — When the Aspire CLI is invoked from inside a known coding agent environment (GitHub Copilot CLI, VS Code Copilot agent, etc.) the agent name is included in the main CLI telemetry event. GitHub Copilot CLI is specifically identified as `copilot-cli`. ([#18240](https://github.com/microsoft/aspire/pull/18240), `@damianedwards`) ### 🏷️ Housekeeping - 📄 Refreshed the `@microsoft/aspire-cli` npm package README to be TypeScript-only — updated examples to the current `ts-starter` template (`apphost.mts` / `aspire.mjs`), added a backing-services snippet showing `aspire add` for PostgreSQL and Redis, and documented `aspire dashboard run` as a standalone dashboard option. ([#18221](https://github.com/microsoft/aspire/pull/18221), `@adamint`) --- _Full Changelog: [v13.4.4...v13.4.5](https://github.com/microsoft/aspire/compare/v13.4.4...v13.4.5)_ _Full commit: [73114e86c64aeb9f3f3c7da8e37df1ae4281b27e](https://github.com/microsoft/aspire/commit/73114e86c64aeb9f3f3c7da8e37df1ae4281b27e)_ > Generated by [Generate release notes for a new stable Aspire release](https://github.com/microsoft/aspire/actions/runs/27667814104/agentic_workflow) · ● 4.4M <!-- gh-aw-agentic-workflow: Generate release notes for a new stable Aspire release, engine: copilot, version: 1.0.40, model: claude-sonnet-4.6, id: 27667814104, workflow_id: release-notes-generate, run: https://github.com/microsoft/aspire/actions/runs/27667814104 --> ## 13.4.4 ## What's New in Aspire 13.4.4 Patch release for Aspire 13.4 with improved DCP connection reliability during request execution and consistent `ExcludeFromMcp()` filtering across all CLI MCP tools. ### 🐛 Fixes * 🔌 **DCP requests could fail permanently when the connection dropped mid-request** — If the underlying DCP channel closed while a request was in flight, the error was surfaced directly instead of being retried. Reconnection is now attempted as part of the DCP request retry path so transient disconnections recover automatically without surfacing errors. ([#18096](https://github.com/microsoft/aspire/pull/18096), `@karolz-ms`) * 🔍 **Resources marked with `ExcludeFromMcp()` were not consistently filtered from CLI MCP tools** — Resources with the `resource.excludeFromMcp` property were not excluded uniformly from all CLI MCP tool results. `list_resources`, `list_console_logs`, `execute_resource_command`, `list_structured_logs`, `list_traces`, and `list_trace_structured_logs` all now honor the exclusion, preventing excluded resources and their telemetry from appearing in agent context. ([#18150](https://github.com/microsoft/aspire/pull/18150), `@JamesNK`) ### 🏷️ Housekeeping * 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. ([#18093](https://github.com/microsoft/aspire/pull/18093), `@adamratzman`) * * * _Full Changelog: [v13.4.3...v13.4.4](https://github.com/microsoft/aspire/compare/v13.4.3...v13.4.4)_ _Full commit: [ccc566c5ab3285c9beb8f38ede34734bb477c029](https://github.com/microsoft/aspire/commit/ccc566c5ab3285c9beb8f38ede34734bb477c029)_ ## 13.4.3 ## What's New in Aspire 13.4.3 Patch release for Aspire 13.4 with a fix for persistent container endpoint allocation regressions introduced in 13.4. ### 🐛 Fixes - 🔌 **Persistent container endpoints had incorrect default behavior** — Persistent containers were defaulting to proxyless endpoint behavior instead of the proxied behavior used by normal containers. This caused integrations that depend on endpoint allocation before resource startup (such as the KeyVault emulator) to fail. Persistent containers now default to proxied endpoints matching normal container behavior; opt out with `isProxied: false` or `WithEndpointProxySupport(false)`. Proxyless container endpoints with only …
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of the internal fix for strict SemVer validation of playwrightCliVersion.