Lack of SignalR typescript client release notes

[alex-airbox]

I'm unable to find any kind of release notes for the TS library of SignalR. There's not even a readme here:
https://github.com/dotnet/aspnetcore/tree/main/src/SignalR/clients/ts

And no links to changelogs here either:
https://www.npmjs.com/package/@microsoft/signalr

I can see the versions numbers go up... no idea what has changed.

[BrennanConroy]

There's not even a readme here:
https://github.com/dotnet/aspnetcore/tree/main/src/SignalR/clients/ts

Well the readme would be in the individual projects, so:
https://github.com/dotnet/aspnetcore/tree/main/src/SignalR/clients/ts/signalr
But I could see it being useful to include a readme in the clients/ts/ folder just to give some info about the folder structure and what is there.

I'm unable to find any kind of release notes for the TS library of SignalR

Because we're a large repo that contains a lot more than just the TS library for SignalR there is no easy way to generate (and provide) release notes. Github also doesn't support diffing between versions for a specific directory. The closest you could get is manually looking at the commits from two releases.
e.g. https://github.com/dotnet/aspnetcore/commits/release/7.0/src/SignalR/clients/ts/signalr and https://github.com/dotnet/aspnetcore/commits/release/8.0/src/SignalR/clients/ts/signalr
Looks like there were ~13 commits to the @microsoft/signalr project between 7.0 and 8.0

[rallets]

Hi I agree with @alex-airbox, @BrennanConroy ! I would like to update a typescript client app and I struggled to find some info about what is changed between 7 and 8... Breaking changes? It's safe to upgrade? What is the migration process? What should I test? and so on. Very very bad DX. It's a standard for each npm package to point to a changelog/release note. If you want JavaScript/typescript to embrace signalr this is a minimum level of info to provide. I cannot spend hours every time I need to upgrade, not only for major versions, but also for bug fix and minor changes. I expect a little bit more from Microsoft to be honest.
Or is signalr been deprecated and we need to look to something else? Because the message you send out is exactly this: we don't have time to support this package.

[leniency]

It's mid-2025 and just saw the npm package got bumped from 8 to 9.0.6. Still no release notes or summary of changes, short of attempting to dig through individual files and commits. No release listed under the github releases.

[sicin]

How can I find what's changed between version 8.0.7 and 8.0.18?

[martincostello]

How can I find what's changed between version 8.0.7 and 8.0.18?

You can view the diff, change to the Files changed tab, then search for signalr/clients/ts - the changes appear near the bottom of the diff.

[BrennanConroy]

I'm thinking of putting a CHANGELOG.MD file at https://github.com/dotnet/aspnetcore/tree/main/src/SignalR/clients/ts and link to that from the npm package pages. Then every time we make a change we'll update the changelog file. (might want to add a script to our CI to make sure this happens)

Example of what it could look like below. Did a cleanup pass to remove infrastructure changes that shouldn't affect how the package/code behaves, but could preserve those if it's still interesting to have a full list of changes.

SignalR JS/TS Client Changelog

v10.0.0-preview.1.25120.3

• Replaced deprecated substr usage with substring #58732
• Bumped ws dependency to fix component vulnerability #57536
• Bumped webpack from 5.93.0 to 5.94.0 #57592

v9.0.0

• Bumped ws dependency to address security vulnerability #58458

v9.0.0-rc.2.24474.3

• Added Partitioned flag to cookie for SignalR browser testing #57997

v9.0.0-preview.7.24406.2

• Reverted split Node dependency workaround due to issues #56766

v9.0.0-preview.1.24081.5

• Updated Karma config #53247
• Node.js and npm infrastructure improvements #53154
• Improved error handling in SignalR client: rejected promises in invocation messages #52523
• Reordered SignalR message parameters for better readability #51559

v8.0.12

• Updated serialize-javascript dependency #58466

v8.0.10

• Upgraded ws from 7 to 7.5.10 #57411

v8.0.7

• Reverted incorrect handling of Node dependency splitting #55229
• Fixed error handling for rejected promises in incoming Invocation messages #55230

v8.0.2

• Updated Karma config #53411

v8.0.0-rc.2.23480.2

• Introduced Stateful Reconnect support in SignalR #49940
• Renamed internal UseAck to UseStatefulReconnect #50407
• Incremented HubProtocol version for Stateful Reconnect #50442

v8.0.0-preview.7.23375.9

• Removed __non_webpack_require__ workaround, improved Node dependency handling #48154

v8.0.0-preview.6.23329.11

• SignalR client now sends CloseMessage to server #48577

v8.0.0-preview.5.23302.2

• Fixed cookie handling with Fetch API on Node 18+ #48076

v8.0.0-preview.4.23260.4

• Upgraded Webpack for SignalR builds #47403

v8.0.0-preview.1.23112.2

• Fixed CompletionMessage handling for false/null result values #45169
• Enabled ServerTimeout and KeepAliveInterval options in HubConnectionBuilder #46065
• Migrated links to learn.microsoft.com #46206