SignalR-Mastery
SignalR-Mastery copied to clipboard
Update dependency Microsoft.Azure.SignalR to 1.27.0
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
Microsoft.Azure.SignalR (source) | 1.8.0 -> 1.27.0 |
Release Notes
azure/azure-signalr (Microsoft.Azure.SignalR)
v1.27.0
: SDK
What's Changed
- Fix message order issue https://github.com/Azure/azure-signalr/issues/1655 with https://github.com/Azure/azure-signalr/pull/2023
- Cleanup the version deps by @vicancy in https://github.com/Azure/azure-signalr/pull/2029
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.26.1...v1.27.0
v1.26.1
: Release SDK v1.26.1
Newly added
- Add connection FlowControl messages by @terencefan in https://github.com/Azure/azure-signalr/pull/1964
- update swagger to
2023070
by @terencefan in https://github.com/Azure/azure-signalr/pull/1957
Bug fixes
- fix blazor server for 1.26.0. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/2022
- Fix the ack message issue when MapHub for the same hub is called multiple times by @vicancy in https://github.com/Azure/azure-signalr/pull/2021
New Contributors
- @phanthaiduong22 made their first contribution in https://github.com/Azure/azure-signalr/pull/2019
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.26.0...v1.26.1
v1.26.0
What's Changed
New Features
- Support stateful reconnect for .net8 SignalR clients
- add allowing stateful reconnects in server handshake message. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1935
- Add service messages for stateful reconnect. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1923
- Skip unknown extension members. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1932
- Support for partial messages for stateful reconnect. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1930
- Add close in DataMessageType. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1947
- identify message type for connection data message by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1938
- set AllowStatefulReconnects in server connection handshake. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1946
- public allow stateful reconnects in service options. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1950
Improvements
- Use limited pipe for a client connection so that large messages could be pushed back
- switch to limited pipe. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1945
- fix multi-thread writing in client connection context for switching to bounded pipe by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1949
- Update meta info for Microsoft.Azure.SignalR.Serverless.Protocols by @Y-Sindo in https://github.com/Azure/azure-signalr/pull/1910
- Print out the full stack for better local debug experience by @vicancy in https://github.com/Azure/azure-signalr/pull/1927
- upgrade dependencies. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1931
- minor update for arraydict. by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1936
- Rebrand AAD to Microsoft Entra by @terencefan in https://github.com/Azure/azure-signalr/pull/1941
- Suppress 403 when try getting access key by @terencefan in https://github.com/Azure/azure-signalr/pull/1943
- upgrade azure.identity to 1.11.4 by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1958
Bug Fixes
- Dispose should close the server connection by @vicancy in https://github.com/Azure/azure-signalr/pull/1960
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.25.1...v1.26.0
v1.25.1
What's Changed
- Check
AuthenticateResult
ofIAuthenticateResultFeature
is notnull
. by @maliming in https://github.com/Azure/azure-signalr/pull/1918
New Contributors
- @maliming made their first contribution in https://github.com/Azure/azure-signalr/pull/1918
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.25.0...v1.25.1
v1.25.0
What's Changed
- Add to AddNamedAzureSignalR by @vicancy in https://github.com/Azure/azure-signalr/pull/1915
- Add more system claims and 'sub' support by @vicancy in https://github.com/Azure/azure-signalr/pull/1916
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.24.0...v1.25.0
v1.24.0
What's Changed
- Remove jwt token dependency by @vicancy in https://github.com/Azure/azure-signalr/pull/1897
- Remove generated REST client which depends on deprecated package. by @Y-Sindo in https://github.com/Azure/azure-signalr/pull/1902
- Fix UI Culture bug by @xingsy97 in https://github.com/Azure/azure-signalr/pull/1901
v1.23.0
What's Changed
- Support client results in sharding mode by @xingsy97 in https://github.com/Azure/azure-signalr/pull/1852
- Remove net3.0 support by @vicancy in https://github.com/Azure/azure-signalr/pull/1860
- Fix vulnerability by @vicancy in https://github.com/Azure/azure-signalr/pull/1874
- Fix disposed issue when app shut down by @vicancy in https://github.com/Azure/azure-signalr/pull/1876
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.22.0...v1.23.0
v1.22.0
Features
- Add retry capability to REST client to handle transient errors (#1844)
Fixes
- Improve TimerAwaitable for allow Stop to be called multiple times (#1856)
- Normalize the DefaultEndpointRouter weight using unit to make the routing more friendly to AutoScale (#1851)
v1.21.7
Features
- Partial support client invocation in sharding mode by @JialinXin in https://github.com/Azure/azure-signalr/pull/1828.
v1.21.6
Features
- Increase
AuthorizeTimeout
to 100s by @ranjithsnair in https://github.com/Azure/azure-signalr/pull/1812. - Support echo ping to evaluate latency by @vwxyzh in https://github.com/Azure/azure-signalr/pull/1821.
v1.21.5
Features
Fixes
v1.21.4
Bug Fix
Don't throw exceptions when connection is not found in adding connection to group and closing connection REST APIs
v1.21.3
: Release 1.21.3
What's Changed
- Update swagger
2022060
by @xingsy97 in https://github.com/Azure/azure-signalr/pull/1772 - Use sticky service connections for ackable messages by @KKhurin in https://github.com/Azure/azure-signalr/pull/1779
- Add retry logic for AadAccessKey.GenerateToke by @terencefan in https://github.com/Azure/azure-signalr/pull/1785
Full Changelog: https://github.com/Azure/azure-signalr/compare/v1.21.2...v1.21.3
v1.21.2
Bug Fixes
- Fix Json Hub Protocol case sensitive bug #1759 .
v1.21.0
Features:
The transient mode of Management SDK now supports MessagePack in the SDK-side. See MessagePack serialization for more details.
v1.20.0
Features:
The persistent mode of Management SDK now supports MessagePack. See MessagePack serialization for more details.
v1.19.2
This release contains only internal engineering changes. For SignalR function extensions users, this version is incompatible with current SignalR function extensions versions by design. Next SignalR function extensions version will adapt to the change.
v1.19.1
Bug Fixes
- Fix
RemoveConnectionFromAllGroups
in Microsoft.Azure.SignalR.Management #1721. - Fix #1720 : Dependency break in Microsoft.Azure.SignalR.Management #1723.
Improvements
- Add
IAccessTokenProvider
to help differentiate token types #1719. - Optimize log level for connection drops #1722.
v1.19.0
Features:
- Support SignalR
client result
(.NET7.0
+). - Support CloseOnAuthenticationExpiration. Set this option to enable authentication expiration tracking which will close connections when a token expires.
Bug Fixes
- Fix #1652: Configuration issue and a few improvements #1654.
- Fix #1679:
HubConnectionContext.UserIdentifier
is null if negotiation with Management SDK and set user ID #1691. - Fix #1700: proxy not applied to serverless transient mode #1708.
Improvements
- Reduce retry interval when AAD auth failed #1451.
v1.18.3
Features:
- Add 2 properties
InitialHubServerConnectionCount
andMaxHubServerConnectionCount
and obsoleteConnectionCount
Bug Fixes
- Fix https://github.com/Azure/azure-signalr/issues/1652: read ApplicationName from configuration
Azure:SignalR:ApplicationName
https://github.com/Azure/azure-signalr/pull/1651 - Fix the error log that don't log 401 exceptions when the old key is available https://github.com/Azure/azure-signalr/pull/1659
v1.18.1
Bug Fixes
- Fix https://github.com/Azure/azure-signalr/issues/1602: Obsolete UseAzureSignalR when the framework is >= netcoreapp3.0 https://github.com/Azure/azure-signalr/pull/1605
- Fix https://github.com/Azure/azure-signalr/issues/1632: Improve the process outgoing pipeline logic when client connection is closed https://github.com/Azure/azure-signalr/pull/1631
v1.18.0
: Release 1.18.0
Feature
- Add
AuthType=azure
,AuthType=azure.msi
,AuthType=azure.app
supports for connection string.
v1.17.1
: Release 1.17.1
Bug Fixes
- Fix the Azure Function binding issue https://github.com/Azure/azure-signalr/issues/1603
v1.17.0
: Release 1.17.0
Bug Fixes
- Fix the regression issue that for the single endpoint scenario, send message failure does not throw (https://github.com/Azure/azure-signalr/pull/1582)
- Improve the error handling when a message fails to send with multiple endpoints (https://github.com/Azure/azure-signalr/pull/1582)
- "DefaultMessageRouter" filters out "offline" endpoints so that messages will not send out to offline endpoints
- You can customize your own message router if you'd like to make sure exceptions throw when some endpoints are offline.
- Fix the endpoint hot-reload logic to support "ClientEndpoint" and "ServerEndpoint" property (https://github.com/Azure/azure-signalr/pull/1592)
v1.16.1
Features
- Add server endpoint and client endpoint as optional parameters of a
ServiceEndpoint
constructor so that users can customize them with AAD auth. #1586
public ServiceEndpoint(Uri endpoint, TokenCredential credential, EndpointType endpointType = EndpointType.Primary, string name = "", Uri serverEndpoint = null, Uri clientEndpoint = null)
Fixes
- Fixes the ackable message time out problem when multiple SignalR endpoints exist. #1576
v1.16.0
Features
- Support the customization of endpoints for servers to connect to ASRS in code or config. #1564
Users have two ways to set
serverEndpoint
orclientEndpoint
.- Option 1: in connection string:
serverEndpoint=...
- Option 2: in the ctor of
ServiceEndpoint
:new ServiceEndpoint(new Uri(endpoint), new DefaultAzureCredential()) { ClientEndpoint = clientEndpoint, ServerEndpoint = serverEndpoint }
- Option 1: in connection string:
- Allow customization of endpoints for clients to connect to ASRS in code.#1564 See the code sample above.
- Expose connection capacity in metrics of ServiceEndpoint #1567
- Change the default endpoint router from random to weighted random #1568
Fixes
- Fix the message order problem with multiple service connections. #1571
v1.15.2
Fixes
- Fix the bug that Management SDK connection count is fixed to 3
-
RestClient
SetStatusCode
onHttpRequestException
on .NET 5 or above runtime.
v1.15.1
Fixes
- Fix dismatch behavior of empty userIs in
IHubContext<THub, T>.Clients.Users(userIds).Method
, between AspNetCore SignalR and SignalR service SDK #1544
Improvements
- Improve cross-project debug experience by enabling source link. #1546
v1.15.0
Fixes
- Fix negotiation error when using AAD and multiple endpoints. #1530
- Fix
Newtonsoft.Json
version conflicts which might cause some failures such as AAD auth and REST API calls. #1520 - Fix a bug in the
RestClient
that causes REST API calls error. #1519 - Fix security issues by updating package versions:
Microsoft.AspNetCore.Http
2.1.0 -> 2.1.22,Microsof.tAspNetCore.Http.Connections
1.0.0 -> 1.0.15,Microsoft.AspNetCore.WebSockets
2.1.0 -> 2.1.7,System.Net.WebSockets.WebSocketProtocol
4.5.0 -> 4.5.3
v1.14.0
Known issue with this version
- We have a bug in this version that would affect:
- AAD authentication
- In Management SDK Transient transport type (the default one) : group management (such as adding users to groups, removing users from groups), client management (such as checking if user is in group).
Management SDK
- In persistent mode, adding a user to a group, removing a user from a group, removing a user from all groups are confirmed to be finished once the methods in
ServiceHubContext.UserGroups
are returned. - Supports a more flexible way to customize JSON serialization. You can use
ServiceManagerOptions.UseJsonObjectSerializer(...)
method to specify a JSON object serializer.System.Text.Json
orNewtonsoft.Json
are both supported. See Customizing Json Serialization in Management SDK for details.
v1.13.0
Server SDK and Management SDK
- Attempt to fix timeout when adding to group: change ackable messages to go through random connections to reduce the burden of a single connection. #1492
Management
- Now you can get a hub context for a strongly typed hub. See details here.
v1.12.0
Features
Server SDK
- You can use
ServiceOptions.TransportTypeDetector
to set theHttpTransportType
for your SignalR clients. #1469
Management SDK
- In persistent transport type, adding a user to group is no more a "fire-and-forget" action now. When the task finishes, the user is in the group.
Protocols
- New
CloseWithAckMessage
types are added, including subclassesCloseMultiConnectionsWithAckMessage
,CloseConnectionWithAckMessage
,CloseConnectionsWithAckMessage
,CloseUserConnectionsWithAckMessage
,CloseGroupConnectionsWithAckMessage
.
v1.11.0
Features
Management SDK
-
ServiceHubContext
now implementsIDisposable
. - All methods in
ServiceHubContext.ClientManager
are supported with persistent transport type. - Remove limitation on setting
ServiceManagerOptions.ServiceEndpoints
with transient transport type. Now no matter what transport type is, you can useDefaultAzureCredential
as follows:
var serviceManager = new ServiceManagerBuilder().WithOptions(option =>
{
option.ServiceEndpoints = new ServiceEndpoint[] { new ServiceEndpoint(new Uri("https://<your-signalr-name>.service.signalr.net"), new DefaultAzureCredential()) };
})
.BuildServiceManager();
Protocol
- Add more property to GroupBroadcastMessage (#1429)
Bug fixes
- Fix a bug in
ServiceManager.IsServiceHealthy
that throws exception. (#1430)
v1.10.0
Features
- Management SDK publishes a new set of APIs to replace the old APIs mainly to support multiple Azure SignalR instances, but the new set of APIs also provide additional benefits.
- Check Migration guide from version 1.9.x and below to 1.10.0 for migration benefits and steps.
- For users who haven't used Management SDK before, you can read this doc directly for an introduction about Management SDK.
-
ServiceManagerBuilder.Build()
,IServiceManagerBuilder
are obsolete.
- SDK client will also send
AccessKey
request via server connection when using aad auth. [ #1361 ] - Add
ServiceEndpoint
constructor for aad scenario.var endpoint = new ServiceEndpoint(new Uri("https://canary-aad-test.service.signalr.net"), new DefaultAzureIdentity());
-
ServiceEndpoint.Endpoint
will convert its hostname into lowercase even when the given hostname is in uppercase. It will also influence the generated accessToken and URL. RFC4343 -
ServiceEndpoint.Endpoint
will automatically add a port postfix if port=xxx was in the connection string and was not equal to 80 when HTTP or 443 when HTTPS. - According to 5, endpoints with the same hostname but have different ports will NOT be considered equal.
Bug fixes
- Fix a bug that will let migrated connections dropped unexpectedly when the app task on the old server could not stop immediately. [ #1376 ]
Known issues:
- In Management SDK / Serverless SDK,
ServiceHubContext.ClientManager
is not ready withPersistent
transport type.
v1.9.2
Features
- Add a
WithNewtonsoftJson
method forServiceManagerBuilder
(https://github.com/Azure/azure-signalr/pull/1351)
Bug fixes
- Fix https://github.com/Azure/azure-signalr/issues/1346 that DetectedLongRunningApplicationTask warning on each websocket connection (https://github.com/Azure/azure-signalr/pull/1350)
v1.9.1
Improvements
- For ASP.NET Core SignalR, the SDK no longer cancels long-running client hub logic when the client disconnects, this behavior change makes the behavior consistent with the self-host SignalR, the discussion leading to this change is #1318 (#1332)
Bug fixes
- Workaround fix for connection migration (#1342)
v1.9.0
- Remove
Microsoft.Azure.Services.AppAuthentication
dependency. - Add
Azure.Identity
dependency to support modern AAD features.
v1.8.2
Improvements:
- add new service events: BufferFull (#1274)
- Implement SendAllExcept and SendToGroupExcept for transient mode (#1287)
- Improve connection drop logs (#1277)
- add connection stat hook. (#1280)
v1.8.1
- Add support for user-assigned manage identity
- To use user-assigned managed identity, you can add a
ClientId=xxxxx
in your aad connection string.Endpoint=<endpoint>;AuthType=aad;ClientId=<User-Assigned Managed Identity clientId>
- To use user-assigned managed identity, you can add a
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Walkthrough
The project file Scaffold.Web.csproj
has been updated to use a newer version of the Microsoft.Azure.SignalR
package, upgrading from 1.8.0
to 1.27.0
. This change enhances the application's capabilities with Azure SignalR services, potentially improving performance and introducing new features or bug fixes. The code structure remains unchanged, ensuring compatibility while keeping dependencies current.
Changes
Files | Change Summary |
---|---|
.../2_Advanced/11_AzureSignalRService/11_1-DefaultModeWithASPNETCore/Scaffold.Web.csproj | Updated Microsoft.Azure.SignalR package version from 1.8.0 to 1.27.0 . |
Poem
🐰 In fields of code, a change takes flight,
With Azure’s grace, our app shines bright.
From1.8
to1.27
, oh what a leap,
New features and fixes, our joy runs deep!
Let’s hop along, with dependencies fine,
A future of signal, so bright and divine! 🌟
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Tips
Chat
There are 3 ways to chat with CodeRabbit:
- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
-
I pushed a fix in commit <commit_id>.
-
Generate unit testing code for this file.
-
Open a follow-up GitHub issue for this discussion.
-
- Files and specific lines of code (under the "Files changed" tab): Tag
@coderabbitai
in a new review comment at the desired location with your query. Examples:-
@coderabbitai generate unit testing code for this file.
-
@coderabbitai modularize this function.
-
- PR comments: Tag
@coderabbitai
in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:-
@coderabbitai generate interesting stats about this repository and render them as a table.
-
@coderabbitai show all the console.log statements in this repository.
-
@coderabbitai read src/utils.ts and generate unit testing code.
-
@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
-
@coderabbitai help me debug CodeRabbit configuration file.
-
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.
CodeRabbit Commands (invoked as PR comments)
-
@coderabbitai pause
to pause the reviews on a PR. -
@coderabbitai resume
to resume the paused reviews. -
@coderabbitai review
to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. -
@coderabbitai full review
to do a full review from scratch and review all the files again. -
@coderabbitai summary
to regenerate the summary of the PR. -
@coderabbitai resolve
resolve all the CodeRabbit review comments. -
@coderabbitai configuration
to show the current CodeRabbit configuration for the repository. -
@coderabbitai help
to get help.
Additionally, you can add @coderabbitai ignore
anywhere in the PR description to prevent this PR from being reviewed.
CodeRabbit Configuration File (.coderabbit.yaml
)
- You can programmatically configure CodeRabbit by adding a
.coderabbit.yaml
file to the root of your repository. - Please see the configuration documentation for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
Documentation and Community
- Visit our Documentation for detailed information on how to use CodeRabbit.
- Join our Discord Community to get help, request features, and share feedback.
- Follow us on X/Twitter for updates and announcements.