Aspire 13.6.4 Stable Release Delivers Reliability and Security Fixes
Aspire 13.6.4 is now available as a stable patch release, addressing resource startup reliability issues, Azure publishing errors in TypeScript AppHosts, and Unix log permissions. This update includes configuration options for Kubernetes API timeouts and tighter directory access controls.
What changed From the source
The Aspire team has published version 13.6.4 as a stable patch release in the dotnet/aspire repository on October 24, 2026. This version addresses three primary areas: resource startup reliability, Azure publishing behavior in TypeScript AppHosts, and CLI diagnostic log permissions on Unix systems.
To resolve resource startup failures caused by timed-out DCP create requests, the AppHost now verifies resource creation status prior to retrying timed-out or HTTP 504 requests. This prevents premature FailedToStart states when DCP operations actually complete successfully. API operations default to a 40-second timeout with a 20-second allowance before the initial successful operation, while resource creation receives a two-minute recovery budget. Administrators can adjust these thresholds using DcpPublisher:KubernetesApiTimeout, DcpPublisher:KubernetesInitializationAdditionalTimeout, and DcpPublisher:KubernetesCreateRecoveryTimeout settings. Existing watch and log streams remain unaffected by these operation limits.
For TypeScript AppHosts, publishing parameterized Azure enum properties has been corrected. Developers can now assign a bicep.parameter expression to enum-valued provisioning properties, such as Azure Storage SKU names, without encountering type-assignment errors. Type checks for literal values and incompatible expressions continue to function as before.
On Unix platforms, CLI diagnostic logs and log directories now utilize stricter owner-only permissions. Log files receive owner read and write access set to 0600, while dedicated Aspire log directories and newly created custom log directories are restricted to owner-only access set to 0700. Existing custom parent directories and Windows permission behavior are left unmodified.
- Repository: dotnet/aspire
- Tag: v13.6.4
- Release type: Stable release
- Published: 2026-10-24
At a glance · Runtime & Platform
What changedWhy it mattersWho should careUpgrade and migration considerations
Why it matters Analysis
Resource startup timeouts have been a notable pain point in previous 13.6 builds under heavy loads or slower Kubernetes environments. By introducing explicit recovery budgets and verification checks before retrying requests, the framework reduces false-negative startup states and offers fine-grained configuration knobs for timeouts.
The security enhancement regarding Unix diagnostic log permissions is critical for teams operating in shared environments. Because diagnostic logs can expose sensitive information such as dashboard login URLs, restricting file permissions to owner-only access mitigates potential local information disclosure risks.
- Prevents false startup failures under slow Kubernetes conditions
- Resolves type-assignment issues during Azure publishing in TypeScript AppHosts
- Secures sensitive diagnostic data against unauthorized local access on Unix systems
Who should care Analysis
Developers utilizing TypeScript AppHosts with Azure provisioning features will benefit directly from the fix allowing bicep parameter expressions with enum properties. Additionally, teams running .NET Aspire deployments on Unix infrastructure should review the updated file permission defaults for diagnostic logs.
Operators experiencing resource initialization timeouts in 13.6 can utilize the newly exposed configuration settings to tune timeout parameters to match their specific cluster environments.
- TypeScript AppHost developers working with Azure resource provisioning
- Engineers operating Aspire on Unix-based developer workstations or servers
- Teams troubleshooting resource startup timeouts in Kubernetes environments
Upgrade and migration considerations Analysis
The source material does not specify exhaustive step-by-step migration instructions beyond updating to version 13.6.4. Teams deploying on Unix should verify that automated log ingestion tools running outside the primary owner account still retain appropriate read access if required, though standard security best practices recommend owner-only permissions for logs containing dashboard credentials.
Administrators wishing to override default timeout behaviors can explicitly set the DcpPublisher configuration keys mentioned in the release notes, though default values should suffice for most standard configurations.
- Review custom log directory permissions on Unix environments after updating
- Evaluate whether default Kubernetes timeout parameters require adjustment via configuration keys
Sources and further reading
- Release notes for v13.6.4 on GitHub (original source)
Original: “Aspire 13.6.4”, Aspire releases, published 24 Oct 2026, retrieved 24 Oct 2026. This article was drafted with AI assistance from the official source and passed automated fact and quality checks. Spotted a mistake? See our corrections policy.