Repository navigation
Bump Aspire.Hosting.JavaScript and 25 others - #110
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Aspire.Hosting.JavaScript from 13.6.1 to 13.6.5 Bumps Aspire.Hosting.PostgreSQL from 13.6.1 to 13.6.5 Bumps Aspire.Hosting.RabbitMQ from 13.6.1 to 13.6.5 Bumps Aspire.Hosting.Redis from 13.6.1 to 13.6.5 Bumps Marten from 9.49.0 to 9.59.0 Bumps Microsoft.AspNetCore.Authentication.Google from 10.0.12 to 10.0.15 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.12 to 10.0.15 Bumps Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.12 to 10.0.15 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.12 to 10.0.15 Bumps Microsoft.AspNetCore.SignalR.Client from 10.0.12 to 10.0.15 Bumps Microsoft.AspNetCore.SignalR.StackExchangeRedis from 10.0.12 to 10.0.15 Bumps Microsoft.Extensions.Http.Resilience to 10.11.0 Bumps Microsoft.Extensions.ServiceDiscovery from 10.10.0 to 10.11.0 Bumps Microsoft.Extensions.ServiceDiscovery.Yarp from 10.10.0 to 10.11.0 Bumps Microsoft.Extensions.TimeProvider.Testing from 10.10.0 to 10.11.0 Bumps Microsoft.NET.Test.Sdk from 18.10.1 to 18.12.0 Bumps OpenIddict.AspNetCore from 7.7.2 to 7.8.0 Bumps OpenIddict.EntityFrameworkCore from 7.7.2 to 7.8.0 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.21.0 Bumps OpenTelemetry.Extensions.Hosting to 1.21.0 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.19.0 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Http from 1.19.0 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Runtime from 1.19.0 to 1.21.0 Bumps WolverineFx.Marten from 6.49.0 to 6.64.0 Bumps WolverineFx.RabbitMQ from 6.49.0 to 6.64.0 Bumps WolverineFx.RuntimeCompilation from 6.49.0 to 6.64.0 --- updated-dependencies: - dependency-name: Marten dependency-version: 9.59.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.SignalR.StackExchangeRedis dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.Extensions.ServiceDiscovery.Yarp dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Instrumentation.Runtime dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.Marten dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.RabbitMQ dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Aspire.Hosting.JavaScript dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Aspire.Hosting.PostgreSQL dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Aspire.Hosting.RabbitMQ dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Aspire.Hosting.Redis dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Marten dependency-version: 9.59.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Marten dependency-version: 9.59.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.Authentication.Google dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.Identity.EntityFrameworkCore dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenIddict.AspNetCore dependency-version: 7.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenIddict.EntityFrameworkCore dependency-version: 7.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.Marten dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.Marten dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.AspNetCore.SignalR.Client dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Microsoft.Extensions.TimeProvider.Testing dependency-version: 10.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/src/Casino.Api/dev/minor-and-patch-34f0b343b0
branch
November 19, 2026 12:11
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.
Updated Aspire.Hosting.JavaScript from 13.6.1 to 13.6.5.
Release notes
Sourced from Aspire.Hosting.JavaScript's releases.
13.6.5
What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.
🐛 Fixes
🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#22071, 0b6bfe2, @jamesnk)
🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#22071, f017f66, @karolz-ms)
🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The
aspire sdk generate,aspire sdk dump, andaspire sdk exportcommands use isolated working directories under<ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#22071, 1ecd7cc, @sebastienros)🔒 Agent setup no longer writes configuration content to a shared temporary log —
aspire agent initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#22071, c408ec5, @mitchdenny)🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#21348, @joperezr)
Full Changelog: v13.6.4...v13.6.5
Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580
13.6.4
What's New in Aspire 13.6.4
Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.
🐛 Fixes
🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature
FailedToStartstate when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #20691. (#20868, backport of #20752, @danegsta)☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a
bicep().parameter(...)expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#20767, backport of #20557, @sebastienros)🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (
0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#21282, backport of #21276, @mitchdenny)Full Changelog: v13.6.3...v13.6.4
Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf
13.6.3
What's New in Aspire 13.6.3
Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.
🐛 Fixes
🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#21002, backport of #20972, @danegsta)
🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#21215, @danegsta; includes microsoft/dcp#307)
Full Changelog: v13.6.2...v13.6.3
Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976
13.6.2
Full commit: af07e33f8d1ef733645138b3f8e36067d073148d
What's Changed
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
Commits viewable in compare view.
Updated Aspire.Hosting.PostgreSQL from 13.6.1 to 13.6.5.
Release notes
Sourced from Aspire.Hosting.PostgreSQL's releases.
13.6.5
What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.
🐛 Fixes
🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#22071, 0b6bfe2, @jamesnk)
🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#22071, f017f66, @karolz-ms)
🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The
aspire sdk generate,aspire sdk dump, andaspire sdk exportcommands use isolated working directories under<ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#22071, 1ecd7cc, @sebastienros)🔒 Agent setup no longer writes configuration content to a shared temporary log —
aspire agent initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#22071, c408ec5, @mitchdenny)🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#21348, @joperezr)
Full Changelog: v13.6.4...v13.6.5
Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580
13.6.4
What's New in Aspire 13.6.4
Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.
🐛 Fixes
🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature
FailedToStartstate when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #20691. (#20868, backport of #20752, @danegsta)☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a
bicep().parameter(...)expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#20767, backport of #20557, @sebastienros)🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (
0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#21282, backport of #21276, @mitchdenny)Full Changelog: v13.6.3...v13.6.4
Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf
13.6.3
What's New in Aspire 13.6.3
Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.
🐛 Fixes
🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#21002, backport of #20972, @danegsta)
🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#21215, @danegsta; includes microsoft/dcp#307)
Full Changelog: v13.6.2...v13.6.3
Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976
13.6.2
Full commit: af07e33f8d1ef733645138b3f8e36067d073148d
What's Changed
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
Commits viewable in compare view.
Updated Aspire.Hosting.RabbitMQ from 13.6.1 to 13.6.5.
Release notes
Sourced from Aspire.Hosting.RabbitMQ's releases.
13.6.5
What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.
🐛 Fixes
🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#22071, 0b6bfe2, @jamesnk)
🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#22071, f017f66, @karolz-ms)
🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The
aspire sdk generate,aspire sdk dump, andaspire sdk exportcommands use isolated working directories under<ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#22071, 1ecd7cc, @sebastienros)🔒 Agent setup no longer writes configuration content to a shared temporary log —
aspire agent initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#22071, c408ec5, @mitchdenny)🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#21348, @joperezr)
Full Changelog: v13.6.4...v13.6.5
Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580
13.6.4
What's New in Aspire 13.6.4
Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.
🐛 Fixes
🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature
FailedToStartstate when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #20691. (#20868, backport of #20752, @danegsta)☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a
bicep().parameter(...)expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#20767, backport of #20557, @sebastienros)🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (
0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#21282, backport of #21276, @mitchdenny)Full Changelog: v13.6.3...v13.6.4
Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf
13.6.3
What's New in Aspire 13.6.3
Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.
🐛 Fixes
🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#21002, backport of #20972, @danegsta)
🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#21215, @danegsta; includes microsoft/dcp#307)
Full Changelog: v13.6.2...v13.6.3
Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976
13.6.2
Full commit: af07e33f8d1ef733645138b3f8e36067d073148d
What's Changed
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
Commits viewable in compare view.
Updated Aspire.Hosting.Redis from 13.6.1 to 13.6.5.
Release notes
Sourced from Aspire.Hosting.Redis's releases.
13.6.5
What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.
🐛 Fixes
🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#22071, 0b6bfe2, @jamesnk)
🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#22071, f017f66, @karolz-ms)
🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The
aspire sdk generate,aspire sdk dump, andaspire sdk exportcommands use isolated working directories under<ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#22071, 1ecd7cc, @sebastienros)🔒 Agent setup no longer writes configuration content to a shared temporary log —
aspire agent initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#22071, c408ec5, @mitchdenny)🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#21348, @joperezr)
Full Changelog: v13.6.4...v13.6.5
Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580
13.6.4
What's New in Aspire 13.6.4
Patch release for Aspire 13.6 that improves resource startup reliability, fixes Azure publishing with parameterized enum properties in TypeScript AppHosts, and tightens CLI diagnostic log permissions on Unix.
🐛 Fixes
🖥️ Resources could fail to start after a DCP create request timed out — AppHost now checks whether a resource was created before retrying a timed-out or HTTP 504 request, avoiding a premature
FailedToStartstate when DCP completed the operation. API operations default to a 40-second timeout with an additional 20-second allowance before the first successful operation, and resource creation has a two-minute recovery budget. These limits can be configured throughDcpPublisher:KubernetesApiTimeout,DcpPublisher:KubernetesInitializationAdditionalTimeout, andDcpPublisher:KubernetesCreateRecoveryTimeout. Established watch and log streams are not limited by these operation timeouts. Addresses startup timeouts reported in 13.6. Fixes #20691. (#20868, backport of #20752, @danegsta)☁️ TypeScript AppHosts could fail to publish parameterized Azure enum properties — Assigning a
bicep().parameter(...)expression to an enum-valued provisioning property, such as an Azure Storage SKU name, now works instead of failing with a type-assignment error. Type checking for literal values and incompatible expression types is preserved. Fixes a scenario introduced with the Azure provisioning proxy feature in 13.6. (#20767, backport of #20557, @sebastienros)🔒 CLI diagnostic logs now use owner-only permissions on Unix — Log files are restricted to owner read/write access (
0600), including reused files, and the dedicated Aspire logs directory uses owner-only access (0700), repairing existing permissions when needed. Newly created custom log directories also use0700; existing custom parent directories and Windows permission behavior are unchanged. Diagnostic logs can contain sensitive data, including dashboard login URLs, so review them before sharing. (#21282, backport of #21276, @mitchdenny)Full Changelog: v13.6.3...v13.6.4
Full commit: c89352703f78ae46de90fbf751ed8b52b77b89bf
13.6.3
What's New in Aspire 13.6.3
Patch release for Aspire 13.6 that improves resource orchestration reliability by preventing unread resource watches from stalling resource updates and operations.
🐛 Fixes
🖥️ Resource operations could stall when a watch stopped being read — AppHost now closes abandoned watch connections when setup is canceled and keeps reading resource events even when event handlers are slow. Resource event ordering, lifecycle callback dispatch, and the existing periodic reconnection safeguard are preserved. (#21002, backport of #20972, @danegsta)
🔄 Slow watchers could block other resource updates or watcher shutdown — The bundled Developer Control Plane (DCP) is updated to 0.26.6, which keeps internal lifecycle watches draining and uses bounded, asynchronous watch delivery to prevent unread watches from blocking resource-change publication and unrelated watcher shutdown. (#21215, @danegsta; includes microsoft/dcp#307)
Full Changelog: v13.6.2...v13.6.3
Full commit: 38294b1b31552dae42a516cffa0cbc737ec08976
13.6.2
Full commit: af07e33f8d1ef733645138b3f8e36067d073148d
What's Changed
Full Changelog: microsoft/aspire@v13.6.1...v13.6.2
Commits viewable in compare view.
Pinned Marten at 9.59.0.
Release notes
Sourced from Marten's releases.
9.59.0
Marten 9.59.0 moves to JasperFx 2.102.0 and Weasel 9.50.0. It adds read-only DCB tag queries on a query session, reports how old a projection's oldest unprocessed event is, and fixes a shutdown race in the explicit projection coordinator.
Highlights
EventsExistAsync,QueryByTagsAsyncandAggregateByTagsAsyncare now onIQuerySession.Events, so a read-only endpoint no longer needs a document session to read by tags (thanks to new contributor @alekbarszczewski, #5841).FetchForWritingByTagsstill needs a document session. Existing calls throughIDocumentSession.Eventsare unchanged, both in source and in compiled assemblies. A class that implementsMarten.Events.IQueryEventStoreitself has three more members to implement.IEventDatabase.FetchFirstEventTimestampsAfterAsync. It returns the timestamp of the oldest event a shard hasn't processed yet, in one round trip. CritterWatch uses it to report projection lag as time instead of a count of events (#5844).StopAsync/PauseAsynccalls, such as the second stop JasperFx'sRunCommandissues whenWebApplicationFactoryor Alba stops the host, no longer stop and dispose the same daemons twice or log "Error while trying to stop daemon agents". A start that overlaps a stop no longer starts a disposed daemon, and a daemon resolved during a stop is no longer dropped without being disposed (#5842, #5843).db-*commands (db-apply,db-assert,db-patch,db-dump,db-list) now appear and run there too. JIT applications see no change (#5840, #5845).AutoCreate, apply at startup,db-apply/resources setupas a deployment step, ordb-patchscripts for a DBA, with links to the Weasel CLI and JasperFx stateful resource docs (#5839).What's Changed
New Contributors
Full Changelog: JasperFx/marten@v9.58.0...V9.59.0
9.58.0
Marten 9.58.0 moves to JasperFx 2.100.0 and Weasel 9.49.0, and makes per-tenant composite rebuilds work on per-tenant partitioned stores.
Highlights
pk_mt_event_progression(#5829, #5833).FetchForExclusiveWritingin a batch throwsStreamLockedExceptionon a locked stream (thanks to new contributor @esond).LogFactoryis set when a customIMartenLoggeris configured.What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.57.0...v9.58.0
9.57.0
Highlights
ShouldDeleteorDeleteEvent<T>, used to lose its whole history to an empty snapshot. Compaction now leaves it alone and logs an information line. (#5797)IncludeStreamandIncludeEventsused to leave those rows in plain text and report success. (#5797)opts.Events.AutoDiscoverTagTypesturns off automatic DCB tag type registration, for stores that use strong-typed identifiers but not DCB. It's on by default, and explicitRegisterTagType<T>()calls work either way. Thanks to @gschuager for the report and the design. (#5806)EventStoreUsagereports the event store'sTenancyStyle, so a console can tell conjoined events from conjoined documents. (#5805)Action needed after upgrading
If you rely on masking for archived or skipped events: run the same
ApplyEventDataMaskingcall again. Data that was archived or skipped when you last ran it is still in plain text until you do.That call runs your rules again over everything the first pass reached. If a rule isn't safe to run twice, such as one that draws a new pseudonym, add
x.IsArchivedto anIncludeEventsfilter that still names the same subject:Never use
x.IsArchivedas the whole filter, because that masks every archived event in the store.If you compact streams: the deleted events can't be rebuilt from Marten. To find affected streams, replace
<schema>and run this, then restore those streams from a backup or from wherever an archiver copied them:An archiver closed over
IDocumentSessionwas never called for past compactions, so that copy won't exist.Behaviour changes
IncludeEventsnow includes archived events. A masking filter that needs only live events should add!x.IsArchived.IDocumentOperationsorIDocumentSessionnow throwsInvalidOperationExceptionbefore anything is queued. It used to be skipped silently, with the events deleted anyway. An archiver closed overIDocumentSessionis now called.ToParameterTypenow throws for an unmapped type where it used to return a character catch-all. An enum resolves through its underlying type, so along-backed enum givesBigint. Marten's own call sites are not affected.What's Changed
Full Changelog: JasperFx/marten@v9.56.0...V9.57.0
... (truncated)
9.56.0
What's Changed
Full Changelog: JasperFx/marten@V9.55.0...v9.56.0
9.55.0
Read before upgrading
Apps running under a Turkish or Azerbaijani culture (
tr-TR,az-AZ) with document types whose names contain an uppercaseI. Document aliases (#5778),DdlTemplatelookups and flat-table upsert function names (#5783) are now lowered with the invariant culture. Before this release, those cultures turnedIinto a dotlessı, so a document typeInvoicewas stored inmt_doc_ınvoice. From 9.55.0 it maps tomt_doc_invoice, and Marten will create that table empty. Rename the existing tables (and their upsert functions) to the invariant name before upgrading, or the existing documents will appear to be missing. Apps on any other culture are unaffected: the names they generate are unchanged.Behaviour change:
StoredDocument.Versionfor projection documents (#5773). For a mapping that usesUseVersionFromMatchingStreamwith revisions, the diagnostics version token is now<mt_version>:<mt_last_modified as epoch microseconds>(or an md5 of the document body when last-modified tracking is disabled). It used to bemt_versionalone, which did not change when the daemon rewrote the document at the same stream version. Anything that parsed the token as an integer must be updated. Undeleting a projection document through the diagnostics writer also no longer bumpsmt_versionpast the stream's version.Fixes worth calling out
x.Inner.Value, instead of falling back to the JSONB path.TrackConnections = TrackLevel.Verbose, amarten.append.eventactivity event is now emitted on every append route, including the Quick routes that are the V9 default. Expect more events per append than before.DatabaseSchemaNamethat is a reserved word or contains uppercase. Before, every schema apply after the first failed with42P07(weasel#750, contributed by @marc-RocketRez).StreamPagedByCursorwrites each page's bytes directly and disposes its pooled stream (#5776, @chrisbbe).What's Changed
New Contributors
Full Changelog: JasperFx/marten@v9.54.2...V9.55.0
9.54.2
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.54.1...v9.54.2
9.54.1
Full Changelog: JasperFx/marten@V9.54.0...V9.54.1
9.54.0
Full Changelog: JasperFx/marten@v9.53.0...V9.54.0
9.53.0
9.53.0 is a minor release. It picks up JasperFx 2.94.0 and implements the three members that release adds, for CritterWatch's Document Store Explorer and Event Store Explorer (#5756).
New
IReadOnlyEventStore.QueryEventData<T>(tenantId)(jasperfx#1073): store-agnostic LINQ over the bodies of one event type, across every stream. It runs through the sharedDocumentQueryableExtensionsterminators (ToListAsync,CountAsync,AnyAsync,FirstOrDefaultAsync).QueryRawEventDataOnly<T>()under the shared name. Events in archived streams are excluded, as they are there.BadLinqExpressionExceptionnaming it.QueryStreamStates:NotSupportedException;IDocumentStoreDiagnosticsWriter.PreviewDocumentJsonAsync(jasperfx#1071): a dry run ofSaveDocumentJsonAsync.ExpectedVersion.DocumentTypeRef.IsSoftDeleted(jasperfx#1070):IDocumentStoreDiagnostics.DocumentTypesAsyncreports whether each type usesDeleteStyle.SoftDelete. A sub-class reports its root mapping's delete style.Compliance
EventDataQueryComplianceis newly enrolled.ReportsDocumentDeleteStyleandSupportsDocumentWritePreviewgates are on.Dependencies
9.52.0
Highlights and behaviour changes
Built on JasperFx 2.93.1.
mt_event_projection_floors. Every event store gets this table as a schema migration on its nextapply (#5740). It holds the persisted projection start floors behind the new
AsyncOptions.SubscribeFromFirstRun().A database whose schema has not been migrated yet keeps starting its projections exactly as before. Floors survive
DeleteAllDocumentsAsync,DeleteAllEventDataAsyncandResetAllData, and they are removed along with a tenant.StoreOptions.Advanced.ExceptionTransforms(#5682). Register your own exception transforms, consultedbefore Marten's built-in ones, to turn a
PostgresExceptionwith your own SQLSTATE into a typed exception.UndeleteDocumentAsync), and ordera document page by last modified, numeric revision or created time ("newest first").
shard reports
ShardFailureCategory.ApplyEventand names the event, where it used to reportOtherwith no event.It is still not dead-lettered, and it was never retried before either.
IEventStore.PreviewHighWaterAdvanceAsync/AdvanceHighWaterMarkToLatestAsync(#5738): preview, thenadvance, the high-water mark to the latest event, the store-agnostic operation CritterWatch calls.
UseTenantPartitionedEventsno longer fails with23503, whether the store has DCB tagrows (#5720) or a
[NaturalKey]aggregate (#5742);intpastint.MaxValue, soILongVersionedworks as #4526 advised (#5723);
UndoDeleteWhere/HardDeleteWhereno longer cause a falseConcurrencyExceptionon a numeric-revision writelater in the same session (#5743).
Aspire.AppHost.Sdk13.6.3 with a PostgreSQL resource. The NuGet publish workflow nolonger installs the obsolete aspire workload (#5724).
What's Changed
Full Changelog: JasperFx/marten@v9.51.0...v9.52.0
9.51.0
What's Changed
Full Changelog: JasperFx/marten@V9.50.3...v9.51.0
9.50.3
The Native AOT and hard-delete release. One new feature on the event store, two schema-naming fixes that could not be worked around, and three behaviour changes — read those before upgrading.
New
TombstoneStream— a hard stream delete (#5673, #5674).session.Events.TombstoneStream(id)queues a single-statement delete of a stream's tag rows, its events and its stream row — plus themt_streams_identityrow under strict identity enforcement — scoped to the session tenant under conjoined tenancy. The event sequence is never touched, and projected documents are deliberately left alone. Queued untilSaveChangesAsync, like every other write.It is on the shared
IEventStoreOperationscontract as a default member that throwsNotSupportedException, so a store without a hard delete stays source-compatible, and the sharedStreamTombstoningCompliancesuite now runs against Marten.DCB tag types can be registered for Native AOT (#5649, #5674, #5676).
RegisterTagType<TTag>()discovers the tag's inner type by reflecting over its members and closes a generic registration at runtime, neither of which a native image can do — so a store with a DCB tag type could not even be configured under AOT.Naming the inner type closes the generic at compile time and the unwrapper replaces the reflection. The suffix is optional and defaults to the tag type's own name, so for a tag the inferring overload could register, this one registers the same inner type and the same table. It works identically under a JIT.
The inferring overloads are now annotated
[RequiresUnreferencedCode]/[RequiresDynamicCode], and — because an analyzer warning only reaches an application that is itself AOT-analyzed, while a store configured from inside a library gets nothing — a failure at runtime now throws naming the exact line to write, keeping the original exception as its inner exception. Automatic tag registration from projection identities logs a warning naming the same line, including the projection'sForAggregate<T>().With explicit registrations, tagging, tag rules,
EventTagQuery,EventsExistAsync,AggregateByTagsAsyncandFetchForWritingByTagsinto a[BoundaryAggregate]all run from a native binary. A CI job publishes and runs them.Fixed
A custom foreign key name is no longer discarded under conjoined tenancy (#5672, #5678). Moving
tenant_idto the front of a document foreign key regenerated the key's name unconditionally, so a name set through theforeignKeyConfigurationcallback was thrown away. That is what made the identifier-length failure unfixable: the exception tells you to override the database object name, and overriding it had no effect. A generated name is still regenerated; a chosen one survives, as does the name of aForeignKeyadded by hand.Archiving a tagged stream no longer fails with a foreign key violation (#5675, #5679). With
UseArchivedStreamPartitioningon and any DCB tag type registered,ArchiveStreamcame back as23503. Eachmt_event_tag_*table is partitioned byis_archivedand carries a composite foreign key tomt_events;mt_archive_streammoved the events between partitions without moving the tag rows that referenced them. It now moves them, in the order that keeps both sides of a non-deferrable key consistent at every statement.AllObjects()no longer applies the Hi-Lo DDL (#5665, #5670). Describing the schema provisioned part of it. The describing seam is now separate from the applying one, and is proven offline against an unreachable host.A failed Rebuild-mode run can be restarted and finished from its committed progress (#5668, #5669).
Performance
Description has been truncated
Dependabo...
Description has been truncated