Bump Aspire.Hosting.Azure.ApplicationInsights and 4 others#35
Bump Aspire.Hosting.Azure.ApplicationInsights and 4 others#35dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
d2bfc9e to
0d5d784
Compare
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughFive Aspire.Hosting packages are updated from 13.3.0 to 13.3.5 in centralized package version management: Azure.ApplicationInsights, Azure.ServiceBus, PostgreSQL, Redis, and SqlServer. ChangesAspire Hosting version bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
084646f to
c818cea
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Directory.Packages.props`:
- Around line 10-14: Bump the Aspire.AppHost.Sdk package to match the
Aspire.Hosting.* minor version: update the Aspire.AppHost.Sdk reference in
NextAurora.AppHost.csproj (or the central Directory.Packages.props entry if it
exists) from 13.3.0 to 13.3.5 so the SDK and runtime packages align; verify
there are no other project-level overrides of Aspire.AppHost.Sdk and run a build
to ensure AppHost startup/orchestration is unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 132f75fd-b889-4748-815d-128d518196ed
📒 Files selected for processing (1)
Directory.Packages.props
c818cea to
6f82eaf
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Directory.Packages.props`:
- Around line 10-14: Update the Aspire.AppHost.Sdk package reference in
NextAurora.AppHost/NextAurora.AppHost.csproj from 13.3.0 to 13.3.5 (or a higher
compatible 13.3.x) so it matches the Aspire.Hosting.* versions; locate the
PackageReference for Aspire.AppHost.Sdk in the NextAurora.AppHost project and
change its Version attribute to 13.3.5, then restore/build to verify no version
conflicts.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 81a517b2-9c9a-4c43-8e94-6f7e0dc6400f
📒 Files selected for processing (1)
Directory.Packages.props
…dabot PR #35 (#62) PR #35 (Dependabot bump of the aspire group) bumps the Aspire.Hosting.* runtime packages from 13.3.0 → 13.3.5 in Directory.Packages.props but does not touch Aspire.AppHost.Sdk, which Dependabot can't see (the SDK pin lives in NextAurora.AppHost.csproj as a <Project Sdk="..."> attribute, not a NuGet PackageVersion). Per CLAUDE.md "Package Management → Aspire SDK and runtime packages must match — including minor versions" — a minor mismatch surfaces at AppHost startup as DCP rejecting startup with "Newer version of the Aspire.Hosting.AppHost package is required." Same trap CodeRabbit flagged on #35. This PR bumps the SDK to 13.3.5 so that: - main has SDK 13.3.5 + packages 13.3.0 (SDK ≥ packages → OK) - After @dependabot rebase on #35: SDK 13.3.5 + packages 13.3.5 (exact match → OK) Once this lands on main, comment `@dependabot rebase` on PR #35 to pick up the new SDK floor and merge. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
|
@dependabot rebase |
1 similar comment
|
@dependabot rebase |
Bumps Aspire.Hosting.Azure.ApplicationInsights from 13.3.0 to 13.3.5 Bumps Aspire.Hosting.Azure.ServiceBus from 13.3.0 to 13.3.5 Bumps Aspire.Hosting.PostgreSQL from 13.3.0 to 13.3.5 Bumps Aspire.Hosting.Redis from 13.3.0 to 13.3.5 Bumps Aspire.Hosting.SqlServer from 13.3.0 to 13.3.5 --- updated-dependencies: - dependency-name: Aspire.Hosting.Azure.ApplicationInsights dependency-version: 13.3.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.Azure.ServiceBus dependency-version: 13.3.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.PostgreSQL dependency-version: 13.3.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.Redis dependency-version: 13.3.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire - dependency-name: Aspire.Hosting.SqlServer dependency-version: 13.3.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: aspire ... Signed-off-by: dependabot[bot] <support@github.com>
6f82eaf to
96f4f51
Compare
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
|
@dependabot rebase |
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
|
Oh no! Something went wrong on our end. Please try again later. If the problem persists, please contact GitHub support for assistance 🙇 |
…isfy S3241 (#64) Main has been broken since #63 (analyzers bump) landed — SonarAnalyzer's S3241 rule now fires on three pre-existing private extension methods in NextAurora.ServiceDefaults/Extensions.cs that return TBuilder but whose callers ignore the return value: - AddOpenTelemetryExporters<TBuilder> (line 107) - AddDefaultAuthentication<TBuilder> (line 169) - AddNextAuroraApiVersioning<TBuilder> (line 234) S3241: "Change return type to 'void'; not a single caller uses the returned value." Every Dependabot rebase since #63 has been failing CI with the same three errors, blocking #35, #36, #61 from merging. Unblocks the queue. The rule is correct — all three were called as statements (`builder.AddOpenTelemetryExporters();`) with the return discarded. Changes the return type to `void`, drops the `return builder;` lines (and converts the early-return in AddDefaultAuthentication from `return builder;` to bare `return;`). No behavior change. No caller change. Build green locally. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Updated Aspire.Hosting.Azure.ApplicationInsights from 13.3.0 to 13.3.5.
Release notes
Sourced from Aspire.Hosting.Azure.ApplicationInsights's releases.
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
aspire publishnow 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)DOTNET_CLI_USE_MSBUILD_SERVER=1for alldotnet run/dotnet buildinvocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that preventedaspire runfrom building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.3.4...v13.3.5
Full commit: 70b33bcb5f64c75e3ab6f57616545f35bd43dc81
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
SKILL.mdgenerated byaspire agent initincluded 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
Full commit: 75080796af797483231a9da2d1642b5130617565
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
Logging__LogLevel__Default=Debugset by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now usesASPIRE_APPHOST_LOGLEVELinstead, which is scoped to Aspire processes only. (#17071, backported via #17078)httpto enable standardhttp+https://service discovery URLs. (#17058, backported via #17063)HostResourceWithEndpoints— Endpoints configured viaHostResourceWithEndpointsare now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092)🏷️ Housekeeping
[SHOULD NOT HAPPEN] failed to update managedFieldserrors. (#17070)Full 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
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 blockedResourceStartingbefore 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
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 runand a DCP bump.🐛 Fixes
aspire runcompute environment validation — Skip compute environment validation in run mode so customers no longer hitResource '<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
Commits viewable in compare view.
Updated Aspire.Hosting.Azure.ServiceBus from 13.3.0 to 13.3.5.
Release notes
Sourced from Aspire.Hosting.Azure.ServiceBus's releases.
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
aspire publishnow 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)DOTNET_CLI_USE_MSBUILD_SERVER=1for alldotnet run/dotnet buildinvocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that preventedaspire runfrom building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.3.4...v13.3.5
Full commit: 70b33bcb5f64c75e3ab6f57616545f35bd43dc81
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
SKILL.mdgenerated byaspire agent initincluded 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
Full commit: 75080796af797483231a9da2d1642b5130617565
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
Logging__LogLevel__Default=Debugset by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now usesASPIRE_APPHOST_LOGLEVELinstead, which is scoped to Aspire processes only. (#17071, backported via #17078)httpto enable standardhttp+https://service discovery URLs. (#17058, backported via #17063)HostResourceWithEndpoints— Endpoints configured viaHostResourceWithEndpointsare now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092)🏷️ Housekeeping
[SHOULD NOT HAPPEN] failed to update managedFieldserrors. (#17070)Full 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
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 blockedResourceStartingbefore 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
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 runand a DCP bump.🐛 Fixes
aspire runcompute environment validation — Skip compute environment validation in run mode so customers no longer hitResource '<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
Commits viewable in compare view.
Updated Aspire.Hosting.PostgreSQL from 13.3.0 to 13.3.5.
Release notes
Sourced from Aspire.Hosting.PostgreSQL's releases.
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
aspire publishnow 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)DOTNET_CLI_USE_MSBUILD_SERVER=1for alldotnet run/dotnet buildinvocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that preventedaspire runfrom building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.3.4...v13.3.5
Full commit: 70b33bcb5f64c75e3ab6f57616545f35bd43dc81
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
SKILL.mdgenerated byaspire agent initincluded 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
Full commit: 75080796af797483231a9da2d1642b5130617565
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
Logging__LogLevel__Default=Debugset by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now usesASPIRE_APPHOST_LOGLEVELinstead, which is scoped to Aspire processes only. (#17071, backported via #17078)httpto enable standardhttp+https://service discovery URLs. (#17058, backported via #17063)HostResourceWithEndpoints— Endpoints configured viaHostResourceWithEndpointsare now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092)🏷️ Housekeeping
[SHOULD NOT HAPPEN] failed to update managedFieldserrors. (#17070)Full 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
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 blockedResourceStartingbefore 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
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 runand a DCP bump.🐛 Fixes
aspire runcompute environment validation — Skip compute environment validation in run mode so customers no longer hitResource '<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
Commits viewable in compare view.
Updated Aspire.Hosting.Redis from 13.3.0 to 13.3.5.
Release notes
Sourced from Aspire.Hosting.Redis's releases.
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
aspire publishnow 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)DOTNET_CLI_USE_MSBUILD_SERVER=1for alldotnet run/dotnet buildinvocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that preventedaspire runfrom building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.3.4...v13.3.5
Full commit: 70b33bcb5f64c75e3ab6f57616545f35bd43dc81
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
SKILL.mdgenerated byaspire agent initincluded 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
Full commit: 75080796af797483231a9da2d1642b5130617565
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
Logging__LogLevel__Default=Debugset by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now usesASPIRE_APPHOST_LOGLEVELinstead, which is scoped to Aspire processes only. (#17071, backported via #17078)httpto enable standardhttp+https://service discovery URLs. (#17058, backported via #17063)HostResourceWithEndpoints— Endpoints configured viaHostResourceWithEndpointsare now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092)🏷️ Housekeeping
[SHOULD NOT HAPPEN] failed to update managedFieldserrors. (#17070)Full 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
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 blockedResourceStartingbefore 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
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 runand a DCP bump.🐛 Fixes
aspire runcompute environment validation — Skip compute environment validation in run mode so customers no longer hitResource '<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
Commits viewable in compare view.
Updated Aspire.Hosting.SqlServer from 13.3.0 to 13.3.5.
Release notes
Sourced from Aspire.Hosting.SqlServer's releases.
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
aspire publishnow 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)DOTNET_CLI_USE_MSBUILD_SERVER=1for alldotnet run/dotnet buildinvocations. On Linux with SDK 10.0.300 this caused a named-pipe timeout that preventedaspire runfrom building the AppHost. The forced override has been removed so the SDK chooses MSBuild server behavior. Fixes #16849. (#17313, backported via #17314)🏷️ Housekeeping
Full Changelog: microsoft/aspire@v13.3.4...v13.3.5
Full commit: 70b33bcb5f64c75e3ab6f57616545f35bd43dc81
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
SKILL.mdgenerated byaspire agent initincluded 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
Full commit: 75080796af797483231a9da2d1642b5130617565
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
Logging__LogLevel__Default=Debugset by the app host was being inherited by all user resources, silently changing their logging verbosity. The app host now usesASPIRE_APPHOST_LOGLEVELinstead, which is scoped to Aspire processes only. (#17071, backported via #17078)httpto enable standardhttp+https://service discovery URLs. (#17058, backported via #17063)HostResourceWithEndpoints— Endpoints configured viaHostResourceWithEndpointsare now correctly materialized, ensuring endpoint resolution and service discovery work as expected. (#17091, backported via #17092)🏷️ Housekeeping
[SHOULD NOT HAPPEN] failed to update managedFieldserrors. (#17070)Full 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
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 blockedResourceStartingbefore 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
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 runand a DCP bump.🐛 Fixes
aspire runcompute environment validation — Skip compute environment validation in run mode so customers no longer hitResource '<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
Commits viewable in compare view.
Summary by CodeRabbit