Skip to content

Bump the dotnet group with 8 updates#8913

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/docs/orleans/dotnet-6114c7cb7d
Open

Bump the dotnet group with 8 updates#8913
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/docs/orleans/dotnet-6114c7cb7d

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 17, 2026

Copy link
Copy Markdown

Updated Aspire.Azure.Data.Tables from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.Azure.Data.Tables's releases.

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, @​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, @​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, @​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, @​adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

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, @​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, @​JamesNK)

🏷️ Housekeeping

  • 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#​18093, @​adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full 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: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Aspire.StackExchange.Redis from 13.4.2 to 13.4.5.

Release notes

Sourced from Aspire.StackExchange.Redis's releases.

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, @​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, @​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, @​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, @​adamint)

Full Changelog: v13.4.4...v13.4.5

Full commit: 73114e86c64aeb9f3f3c7da8e37df1ae4281b27e

Generated by Generate release notes for a new stable Aspire release · ● 4.4M

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, @​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, @​JamesNK)

🏷️ Housekeeping

  • 📦 Improved npm CLI package metadata and hardened npm publish validation in the release pipeline. (#​18093, @​adamratzman)

Full Changelog: v13.4.3...v13.4.4

Full 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: microsoft/aspire@v13.4.2...v13.4.3

Full commit: 4f218933552e18ff2874d1b6d5dc3fe671e3b6d9

Generated by Generate release notes for a new stable Aspire release · ● 4.7M

Commits viewable in compare view.

Updated Microsoft.Orleans.Client from 10.1.0 to 10.2.0.

Release notes

Sourced from Microsoft.Orleans.Client's releases.

10.2.0

Orleans v10.2.0 focuses on runtime reliability, grain directory correctness, observability, Durable Jobs and journaling improvements, provider fixes, and a broad test/CI stabilization push.

Highlights

Breaking changes and notable behavior changes

  • Redis multiplexer ownership: Redis providers using a DI-provided IConnectionMultiplexer via ServiceKey no longer dispose that shared multiplexer on shutdown. Providers which create their own multiplexer still own and dispose it. (#​10146, #​10182)
  • Metrics meter access: the static Orleans meter was removed. Code which referenced Orleans.Runtime.Instruments.Meter should resolve OrleansInstruments from DI and use its Meter instead. (#​10201)
  • Journaling default format: JSON Lines is now the default Orleans.Journaling storage format. Existing journals with stored format metadata continue to be read correctly; legacy entries without metadata are treated as OrleansBinary and migrate on snapshot write. Set JournaledStateManagerOptions.JournalFormatKey = "orleans-binary" to retain the old format for new writes. (#​9973)
  • Silo startup lifecycle: a new ValidateInitialConnectivity stage runs before BecomeActive, keeping silos in Joining until initial peer connectivity is validated. (#​10153)
  • Reminder lifecycle: reminder delivery is gated on the silo becoming active, while reminder register/update/unregister operations remain available later into shutdown. (#​10154, #​10155)
  • Client connection retries: the default client retry filter now retries additional transient gateway/startup failures, including OrleansMessageRejectionException and ConnectionFailedException, with a longer default retry window. (#​10140)
  • Directory activation-failure retries: retry loops after directory activation failures are now bounded by the normal message forward-count budget. (#​10094)
  • Diagnostics listener name: GrainLifecycleEvents.ListenerName is now correctly "Orleans.GrainLifecycle"; code subscribing by the previous string literal should update. (#​10121)
  • Durable Jobs storage providers: custom Durable Jobs journaling providers need catalog support via IJournalStorageCatalog. (#​10112, #​10148)
  • NATS options validation: invalid StorageType enum values are rejected at startup. (#​10176)

Runtime, activation, placement, and lifecycle

  • Fixed a stateless-worker reactivation race and a crash when cancelling indefinite keep-alive tickets. (#​10016, #​10014)
  • Fixed stuck deactivation recovery by removing stranded activations from the catalog, unregistering directory entries, and avoiding stale forwarding loops. (#​10046)
  • Fixed shutdown activations leaving stale grain directory entries. (#​10206)
  • Made the activation collector safer under memory pressure and when there are no valid candidates. (#​10113)
  • Stopped and awaited PlacementService workers during silo shutdown. (#​9993)
  • Prevented persistent stream pulling agents from accepting work or processing queue reads after shutdown starts. (#​10036)
  • Stabilized late lifecycle registration scheduling to avoid lock/scheduler races. (#​10135)
  • Added explicit initial connectivity validation before a silo becomes active. (#​10153)
  • Avoided tracking deactivated grains in activation repartitioner state and fixed repartitioning waits for inactive migrations. (#​10061, #​10130)
  • Reduced runtime hot-path overhead by avoiding per-activation scheduler logger fields, reducing request monitoring memory use, avoiding context capture in outgoing calls, optimizing response completion sources, simplifying InsideRuntimeClient response handling, and removing locks from activation response processing. (#​10118, #​10119, #​10129, #​10127, #​10128, #​10139, #​10141)
  • Broadened the default client connection retry filter to cover more transient startup and gateway failures. (#​10140)

Grain directory, routing, and cache correctness

  • Added TTL cleanup to the grain directory cache and diagnostic hooks for cache state changes. (#​10055)
  • Added a fast-path message destination cache for grain calls, with invalidation on activation, connection, gateway, and client state changes. (#​10064)
  • Capped cache invalidation header growth during message send and deserialization. (#​10078, #​10105)
  • Set target silo metadata correctly on cached silo connections. (#​10080)
  • Capped distributed directory ownership transfer batch sizes and split large transfer payloads into multiple messages. (#​10047, #​10053)
  • Fixed distributed directory recovery handoff for grains activating during ownership transfer. (#​10082)
  • Added distributed remote grain directory compatibility for rolling upgrades and a regression test for directory migration joins. (#​10050, #​10049)
  • Fixed LocalGrainDirectory membership reconciliation using snapshot-based processing, membership-version-aware stale cleanup, and membership refresh before directory RPC routing. (#​10086, #​10087, #​10088)
  • Simplified LocalGrainDirectory membership processing after the reconciliation changes. (#​10089)
  • Refined directory forwarding retry checks, removed a problematic directory failure forwarding optimization, and bounded retries after directory activation failures. (#​10092, #​10095, #​10094)
    ... (truncated)

Commits viewable in compare view.

Updated Microsoft.Orleans.Clustering.Redis from 10.1.0 to 10.2.0.

Release notes

Sourced from Microsoft.Orleans.Clustering.Redis's releases.

10.2.0

Orleans v10.2.0 focuses on runtime reliability, grain directory correctness, observability, Durable Jobs and journaling improvements, provider fixes, and a broad test/CI stabilization push.

Highlights

Breaking changes and notable behavior changes

  • Redis multiplexer ownership: Redis providers using a DI-provided IConnectionMultiplexer via ServiceKey no longer dispose that shared multiplexer on shutdown. Providers which create their own multiplexer still own and dispose it. (#​10146, #​10182)
  • Metrics meter access: the static Orleans meter was removed. Code which referenced Orleans.Runtime.Instruments.Meter should resolve OrleansInstruments from DI and use its Meter instead. (#​10201)
  • Journaling default format: JSON Lines is now the default Orleans.Journaling storage format. Existing journals with stored format metadata continue to be read correctly; legacy entries without metadata are treated as OrleansBinary and migrate on snapshot write. Set JournaledStateManagerOptions.JournalFormatKey = "orleans-binary" to retain the old format for new writes. (#​9973)
  • Silo startup lifecycle: a new ValidateInitialConnectivity stage runs before BecomeActive, keeping silos in Joining until initial peer connectivity is validated. (#​10153)
  • Reminder lifecycle: reminder delivery is gated on the silo becoming active, while reminder register/update/unregister operations remain available later into shutdown. (#​10154, #​10155)
  • Client connection retries: the default client retry filter now retries additional transient gateway/startup failures, including OrleansMessageRejectionException and ConnectionFailedException, with a longer default retry window. (#​10140)
  • Directory activation-failure retries: retry loops after directory activation failures are now bounded by the normal message forward-count budget. (#​10094)
  • Diagnostics listener name: GrainLifecycleEvents.ListenerName is now correctly "Orleans.GrainLifecycle"; code subscribing by the previous string literal should update. (#​10121)
  • Durable Jobs storage providers: custom Durable Jobs journaling providers need catalog support via IJournalStorageCatalog. (#​10112, #​10148)
  • NATS options validation: invalid StorageType enum values are rejected at startup. (#​10176)

Runtime, activation, placement, and lifecycle

  • Fixed a stateless-worker reactivation race and a crash when cancelling indefinite keep-alive tickets. (#​10016, #​10014)
  • Fixed stuck deactivation recovery by removing stranded activations from the catalog, unregistering directory entries, and avoiding stale forwarding loops. (#​10046)
  • Fixed shutdown activations leaving stale grain directory entries. (#​10206)
  • Made the activation collector safer under memory pressure and when there are no valid candidates. (#​10113)
  • Stopped and awaited PlacementService workers during silo shutdown. (#​9993)
  • Prevented persistent stream pulling agents from accepting work or processing queue reads after shutdown starts. (#​10036)
  • Stabilized late lifecycle registration scheduling to avoid lock/scheduler races. (#​10135)
  • Added explicit initial connectivity validation before a silo becomes active. (#​10153)
  • Avoided tracking deactivated grains in activation repartitioner state and fixed repartitioning waits for inactive migrations. (#​10061, #​10130)
  • Reduced runtime hot-path overhead by avoiding per-activation scheduler logger fields, reducing request monitoring memory use, avoiding context capture in outgoing calls, optimizing response completion sources, simplifying InsideRuntimeClient response handling, and removing locks from activation response processing. (#​10118, #​10119, #​10129, #​10127, #​10128, #​10139, #​10141)
  • Broadened the default client connection retry filter to cover more transient startup and gateway failures. (#​10140)

Grain directory, routing, and cache correctness

  • Added TTL cleanup to the grain directory cache and diagnostic hooks for cache state changes. (#​10055)
  • Added a fast-path message destination cache for grain calls, with invalidation on activation, connection, gateway, and client state changes. (#​10064)
  • Capped cache invalidation header growth during message send and deserialization. (#​10078, #​10105)
  • Set target silo metadata correctly on cached silo connections. (#​10080)
  • Capped distributed directory ownership transfer batch sizes and split large transfer payloads into multiple messages. (#​10047, #​10053)
  • Fixed distributed directory recovery handoff for grains activating during ownership transfer. (#​10082)
  • Added distributed remote grain directory compatibility for rolling upgrades and a regression test for directory migration joins. (#​10050, #​10049)
  • Fixed LocalGrainDirectory membership reconciliation using snapshot-based processing, membership-version-aware stale cleanup, and membership refresh before directory RPC routing. (#​10086, #​10087, #​10088)
  • Simplified LocalGrainDirectory membership processing after the reconciliation changes. (#​10089)
  • Refined directory forwarding retry checks, removed a problematic directory failure forwarding optimization, and bounded retries after directory activation failures. (#​10092, #​10095, #​10094)
    ... (truncated)

Commits viewable in compare view.

Updated Microsoft.Orleans.Persistence.Redis from 10.1.0 to 10.2.0.

Release notes

Sourced from Microsoft.Orleans.Persistence.Redis's releases.

10.2.0

Orleans v10.2.0 focuses on runtime reliability, grain directory correctness, observability, Durable Jobs and journaling improvements, provider fixes, and a broad test/CI stabilization push.

Highlights

Breaking changes and notable behavior changes

  • Redis multiplexer ownership: Redis providers using a DI-provided IConnectionMultiplexer via ServiceKey no longer dispose that shared multiplexer on shutdown. Providers which create their own multiplexer still own and dispose it. (#​10146, #​10182)
  • Metrics meter access: the static Orleans meter was removed. Code which referenced Orleans.Runtime.Instruments.Meter should resolve OrleansInstruments from DI and use its Meter instead. (#​10201)
  • Journaling default format: JSON Lines is now the default Orleans.Journaling storage format. Existing journals with stored format metadata continue to be read correctly; legacy entries without metadata are treated as OrleansBinary and migrate on snapshot write. Set JournaledStateManagerOptions.JournalFormatKey = "orleans-binary" to retain the old format for new writes. (#​9973)
  • Silo startup lifecycle: a new ValidateInitialConnectivity stage runs before BecomeActive, keeping silos in Joining until initial peer connectivity is validated. (#​10153)
  • Reminder lifecycle: reminder delivery is gated on the silo becoming active, while reminder register/update/unregister operations remain available later into shutdown. (#​10154, #​10155)
  • Client connection retries: the default client retry filter now retries additional transient gateway/startup failures, including OrleansMessageRejectionException and ConnectionFailedException, with a longer default retry window. (#​10140)
  • Directory activation-failure retries: retry loops after directory activation failures are now bounded by the normal message forward-count budget. (#​10094)
  • Diagnostics listener name: GrainLifecycleEvents.ListenerName is now correctly "Orleans.GrainLifecycle"; code subscribing by the previous string literal should update. (#​10121)
  • Durable Jobs storage providers: custom Durable Jobs journaling providers need catalog support via IJournalStorageCatalog. (#​10112, #​10148)
  • NATS options validation: invalid StorageType enum values are rejected at startup. (#​10176)

Runtime, activation, placement, and lifecycle

  • Fixed a stateless-worker reactivation race and a crash when cancelling indefinite keep-alive tickets. (#​10016, #​10014)
  • Fixed stuck deactivation recovery by removing stranded activations from the catalog, unregistering directory entries, and avoiding stale forwarding loops. (#​10046)
  • Fixed shutdown activations leaving stale grain directory entries. (#​10206)
  • Made the activation collector safer under memory pressure and when there are no valid candidates. (#​10113)
  • Stopped and awaited PlacementService workers during silo shutdown. (#​9993)
  • Prevented persistent stream pulling agents from accepting work or processing queue reads after shutdown starts. (#​10036)
  • Stabilized late lifecycle registration scheduling to avoid lock/scheduler races. (#​10135)
  • Added explicit initial connectivity validation before a silo becomes active. (#​10153)
  • Avoided tracking deactivated grains in activation repartitioner state and fixed repartitioning waits for inactive migrations. (#​10061, #​10130)
  • Reduced runtime hot-path overhead by avoiding per-activation scheduler logger fields, reducing request monitoring memory use, avoiding context capture in outgoing calls, optimizing response completion sources, simplifying InsideRuntimeClient response handling, and removing locks from activation response processing. (#​10118, #​10119, #​10129, #​10127, #​10128, #​10139, #​10141)
  • Broadened the default client connection retry filter to cover more transient startup and gateway failures. (#​10140)

Grain directory, routing, and cache correctness

  • Added TTL cleanup to the grain directory cache and diagnostic hooks for cache state changes. (#​10055)
  • Added a fast-path message destination cache for grain calls, with invalidation on activation, connection, gateway, and client state changes. (#​10064)
  • Capped cache invalidation header growth during message send and deserialization. (#​10078, #​10105)
  • Set target silo metadata correctly on cached silo connections. (#​10080)
  • Capped distributed directory ownership transfer batch sizes and split large transfer payloads into multiple messages. (#​10047, #​10053)
  • Fixed distributed directory recovery handoff for grains activating during ownership transfer. (#​10082)
  • Added distributed remote grain directory compatibility for rolling upgrades and a regression test for directory migration joins. (#​10050, #​10049)
  • Fixed LocalGrainDirectory membership reconciliation using snapshot-based processing, membership-version-aware stale cleanup, and membership refresh before directory RPC routing. (#​10086, #​10087, #​10088)
  • Simplified LocalGrainDirectory membership processing after the reconciliation changes. (#​10089)
  • Refined directory forwarding retry checks, removed a problematic directory failure forwarding optimization, and bounded retries after directory activation failures. (#​10092, #​10095, #​10094)
    ... (truncated)

Commits viewable in compare view.

Updated Microsoft.Orleans.Sdk from 10.1.0 to 10.2.0.

Release notes

Sourced from Microsoft.Orleans.Sdk's releases.

10.2.0

Orleans v10.2.0 focuses on runtime reliability, grain directory correctness, observability, Durable Jobs and journaling improvements, provider fixes, and a broad test/CI stabilization push.

Highlights

Breaking changes and notable behavior changes

  • Redis multiplexer ownership: Redis providers using a DI-provided IConnectionMultiplexer via ServiceKey no longer dispose that shared multiplexer on shutdown. Providers which create their own multiplexer still own and dispose it. (#​10146, #​10182)
  • Metrics meter access: the static Orleans meter was removed. Code which referenced Orleans.Runtime.Instruments.Meter should resolve OrleansInstruments from DI and use its Meter instead. (#​10201)
  • Journaling default format: JSON Lines is now the default Orleans.Journaling storage format. Existing journals with stored format metadata continue to be read correctly; legacy entries without metadata are treated as OrleansBinary and migrate on snapshot write. Set JournaledStateManagerOptions.JournalFormatKey = "orleans-binary" to retain the old format for new writes. (#​9973)
  • Silo startup lifecycle: a new ValidateInitialConnectivity stage runs before BecomeActive, keeping silos in Joining until initial peer connectivity is validated. (#​10153)
  • Reminder lifecycle: reminder delivery is gated on the silo becoming active, while reminder register/update/unregister operations remain available later into shutdown. (#​10154, #​10155)
  • Client connection retries: the default client retry filter now retries additional transient gateway/startup failures, including OrleansMessageRejectionException and ConnectionFailedException, with a longer default retry window. (#​10140)
  • Directory activation-failure retries: retry loops after directory activation failures are now bounded by the normal message forward-count budget. (#​10094)
  • Diagnostics listener name: GrainLifecycleEvents.ListenerName is now correctly "Orleans.GrainLifecycle"; code subscribing by the previous string literal should update. (#​10121)
  • Durable Jobs storage providers: custom Durable Jobs journaling providers need catalog support via IJournalStorageCatalog. (#​10112, #​10148)
  • NATS options validation: invalid StorageType enum values are rejected at startup. (#​10176)

Runtime, activation, placement, and lifecycle

  • Fixed a stateless-worker reactivation race and a crash when cancelling indefinite keep-alive tickets. (#​10016, #​10014)
  • Fixed stuck deactivation recovery by removing stranded activations from the catalog, unregistering directory entries, and avoiding stale forwarding loops. (#​10046)
  • Fixed shutdown activations leaving stale grain directory entries. (#​10206)
  • Made the activation collector safer under memory pressure and when there are no valid candidates. (#​10113)
  • Stopped and awaited PlacementService workers during silo shutdown. (#​9993)
  • Prevented persistent stream pulling agents from accepting work or processing queue reads after shutdown starts. (#​10036)
  • Stabilized late lifecycle registration scheduling to avoid lock/scheduler races. (#​10135)
  • Added explicit initial connectivity validation before a silo becomes active. (#​10153)
  • Avoided tracking deactivated grains in activation repartitioner state and fixed repartitioning waits for inactive migrations. (#​10061, #​10130)
  • Reduced runtime hot-path overhead by avoiding per-activation scheduler logger fields, reducing request monitoring memory use, avoiding context capture in outgoing calls, optimizing response completion sources, simplifying InsideRuntimeClient response handling, and removing locks from activation response processing. (#​10118, #​10119, #​10129, #​10127, #​10128, #​10139, #​10141)
  • Broadened the default client connection retry filter to cover more transient startup and gateway failures. (#​10140)

Grain directory, routing, and cache correctness

  • Added TTL cleanup to the grain directory cache and diagnostic hooks for cache state changes. (#​10055)
  • Added a fast-path message destination cache for grain calls, with invalidation on activation, connection, gateway, and client state changes. (#​10064)
  • Capped cache invalidation header growth during message send and deserialization. (#​10078, #​10105)
  • Set target silo metadata correctly on cached silo connections. (#​10080)
  • Capped distributed directory ownership transfer batch sizes and split large transfer payloads into multiple messages. (#​10047, #​10053)
  • Fixed distributed directory recovery handoff for grains activating during ownership transfer. (#​10082)
  • Added distributed remote grain directory compatibility for rolling upgrades and a regression test for directory migration joins. (#​10050, #​10049)
  • Fixed LocalGrainDirectory membership reconciliation using snapshot-based processing, membership-version-aware stale cleanup, and membership refresh before directory RPC routing. (#​10086, #​10087, #​10088)
  • Simplified LocalGrainDirectory membership processing after the reconciliation changes. (#​10089)
  • Refined directory forwarding retry checks, removed a problematic directory failure forwarding optimization, and bounded retries after directory activation failures. (#​10092, #​10095, #​10094)
    ... (truncated)

Commits viewable in compare view.

Updated Microsoft.Orleans.Server from 10.1.0 to 10.2.0.

Release notes

Sourced from Microsoft.Orleans.Server's releases.

10.2.0

Orleans v10.2.0 focuses on runtime reliability, grain directory correctness, observability, Durable Jobs and journaling improvements, provider fixes, and a broad test/CI stabilization push.

Highlights

Breaking changes and notable behavior changes

  • Redis multiplexer ownership: Redis providers using a DI-provided IConnectionMultiplexer via ServiceKey no longer dispose that shared multiplexer on shutdown. Providers which create their own multiplexer still own and dispose it. (#​10146, #​10182)
  • Metrics meter access: the static Orleans meter was removed. Code which referenced Orleans.Runtime.Instruments.Meter should resolve OrleansInstruments from DI and use its Meter instead. (#​10201)
  • Journaling default format: JSON Lines is now the default Orleans.Journaling storage format. Existing journals with stored format metadata continue to be read correctly; legacy entries without metadata are treated as OrleansBinary and migrate on snapshot write. Set JournaledStateManagerOptions.JournalFormatKey = "orleans-binary" to retain the old format for new writes. (#​9973)
  • Silo startup lifecycle: a new ValidateInitialConnectivity stage runs before BecomeActive, keeping silos in Joining until initial peer connectivity is validated. (#​10153)
  • Reminder lifecycle: reminder delivery is gated on the silo becoming active, while reminder register/update/unregister operations remain available later into shutdown. (#​10154, #​10155)
  • Client connection retries: the default client retry filter now retries additional transient gateway/startup failures, including OrleansMessageRejectionException and ConnectionFailedException, with a longer default retry window. (#​10140)
  • Directory activation-failure retries: retry loops after directory activation failures are now bounded by the normal message forward-count budget. (#​10094)
  • Diagnostics listener name: GrainLifecycleEvents.ListenerName is now correctly "Orleans.GrainLifecycle"; code subscribing by the previous string literal should update. (#​10121)
  • Durable Jobs storage providers: custom Durable Jobs journaling providers need catalog support via IJournalStorageCatalog. (#​10112, #​10148)
  • NATS options validation: invalid StorageType enum values are rejected at startup. (#​10176)

Runtime, activation, placement, and lifecycle

  • Fixed a stateless-worker reactivation race and a crash when cancelling indefinite keep-alive tickets. (#​10016, #​10014)
  • Fixed stuck deactivation recovery by removing stranded activations from the catalog, unregistering directory entries, and avoiding stale forwarding loops. (#​10046)
  • Fixed shutdown activations leaving stale grain directory entries. (#​10206)
  • Made the activation collector safer under memory pressure and when there are no valid candidates. (#​10113)
  • Stopped and awaited PlacementService workers during silo shutdown. (#​9993)
  • Prevented persistent stream pulling agents from accepting work or processing queue reads after shutdown starts. (#​10036)
  • Stabilized late lifecycle registration scheduling to avoid lock/scheduler races. (#​10135)
  • Added explicit initial connectivity validation before a silo becomes active. (#​10153)
  • Avoided tracking deactivated grains in activation repartitioner state and fixed repartitioning waits for inactive migrations. (#​10061, #​10130)
  • Reduced runtime hot-path overhead by avoiding per-activation scheduler logger fields, reducing request monitoring memory use, avoiding context capture in outgoing calls, optimizing response completion sources, simplifying InsideRuntimeClient response handling, and removing locks from activation response processing. (#​10118, #​10119, #​10129, #​10127, #​10128, #​10139, #​10141)
  • Broadened the default client connection retry filter to cover more transient startup and gateway failures. (#​10140)

Grain directory, routing, and cache correctness

  • Added TTL cleanup to the grain directory cache and diagnostic hooks for cache state changes. (#​10055)
  • Added a fast-path message destination cache for grain calls, with invalidation on activation, connection, gateway, and client state changes. (#​10064)
  • Capped cache invalidation header growth during message send and deserialization. (#​10078, #​10105)
  • Set target silo metadata correctly on cached silo connections. (#​10080)
  • Capped distributed directory ownership transfer batch sizes and split large transfer payloads into multiple messages. (#​10047, #​10053)
  • Fixed distributed directory recovery handoff for grains activating during ownership transfer. (#​10082)
  • Added distributed remote grain directory compatibility for rolling upgrades and a regression test for directory migration joins. (#​10050, #​10049)
  • Fixed LocalGrainDirectory membership reconciliation using snapshot-based processing, membership-version-aware stale cleanup, and membership refresh before directory RPC routing. (#​10086, #​10087, #​10088)
  • Simplified LocalGrainDirectory membership processing after the reconciliation changes. (#​10089)
  • Refined directory forwarding retry checks, removed a problematic directory failure forwarding optimization, and bounded retries after directory activation failures. (#​10092, #​10095, #​10094)
    ... (truncated)

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.15.3 to 1.16.0.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.16.0

For highlights and announcements pertaining to this release see: Release Notes > 1.16.0.

The following changes are from the previous release 1.16.0-rc.1.

... (truncated)

1.16.0-rc.1

The following changes are from the previous release 1.15.3.

  • NuGet: OpenTelemetry v1.16.0-rc.1

    • Stop validating View-provided metric stream Name against the instrument
      name syntax, per
      spec clarification.
      (#​7300)

    • Fix incorrect validation of OTEL_BSP_* and OTEL_BLRP_* environment
      variables.
      (#​7187)

    • Fix observable instrument callbacks running once per reader instead of
      once per collection cycle.
      (#​7188)

    • Added exception safety for user-supplied ExemplarReservoir implementations.
      Exceptions thrown from Offer are now caught and logged rather than propagating
      out of Counter.Add/Histogram.Record.
      (#​7277)

    • Update OpenTelemetrySdkEventSource to support the W3C randomness flag.
      ([#​7301](https://github.com/open-telemetry...

_Description has been tru...

Description has been truncated

Bumps Aspire.Azure.Data.Tables from 13.4.2 to 13.4.5
Bumps Aspire.StackExchange.Redis from 13.4.2 to 13.4.5
Bumps Microsoft.Orleans.Client from 10.1.0 to 10.2.0
Bumps Microsoft.Orleans.Clustering.Redis from 10.1.0 to 10.2.0
Bumps Microsoft.Orleans.Persistence.Redis from 10.1.0 to 10.2.0
Bumps Microsoft.Orleans.Sdk from 10.1.0 to 10.2.0
Bumps Microsoft.Orleans.Server from 10.1.0 to 10.2.0
Bumps OpenTelemetry.Extensions.Hosting from 1.15.3 to 1.16.0

---
updated-dependencies:
- dependency-name: Aspire.Azure.Data.Tables
  dependency-version: 13.4.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet
- dependency-name: Aspire.StackExchange.Redis
  dependency-version: 13.4.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet
- dependency-name: Aspire.StackExchange.Redis
  dependency-version: 13.4.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Client
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Sdk
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Clustering.Redis
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Clustering.Redis
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Persistence.Redis
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Sdk
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Microsoft.Orleans.Server
  dependency-version: 10.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: OpenTelemetry.Extensions.Hosting
  dependency-version: 1.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants