[Bug]: Floci — AddFlociAzure pins floci-az 0.10.0; bump to 0.11.0 (.NET SDK connectivity fixes) #1553

Package

CommunityToolkit.Aspire.Hosting.Floci

Describe the bug / problem

FlociContainerImageTags.AzureTag pins floci/floci-az to 0.10.0, but 0.11.0 shipped 2026-08-18. 0.11.0 carries fixes .NET SDK users need to connect at all or to get correct behavior, including:

• Service Bus session support ([FEAT] Service Bus: session support (RequiresSession entities + session-based receivers) floci-io/floci-az#123) and subscription CorrelationFilter rules (Aspire.CommunityToolkit.* -> CommunityToolkit.Aspire.* #124) hardening,
• .NET MSSBCBS SASL negotiation (Remove duplicate directory #159) — without it Azure.Messaging.ServiceBus cannot connect,
• Cosmos container/item TTL (There are no versions available for the package 'Aspire.CommunityToolkit.Hosting.Ollama'. #126/Release v8.2.1 #141) and composite-index enforcement (Ollama hosting component should expose resource commands for model management #127).

A further release (post-0.11.0) will carry the recently merged .NET compatibility fixes (batched sends floci-io/floci-az#212, .NET admin-client routing #215, .NET Cosmos queries #216, TransactionalBatch #217) — worth bumping to that as soon as it's tagged.

Expected behavior

The integration defaults to the latest floci-az release (0.11.0 today), and the tag is kept current with upstream releases (Renovate rule or a release-tracking chore).

Additional context

The file has no Renovate annotation, so the const won't auto-bump: src/CommunityToolkit.Aspire.Hosting.Floci/FlociContainerImageTags.cs. Happy to send the one-line PR.