feat(presets): Add nenoNaninu/TypedSignalR.Client

[sommmen]

Changes

Adds https://github.com/nenoNaninu/TypedSignalR.Client

Context

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Do these repos all release synchronized versions at the same time?

[sommmen]

Do these repos all release synchronized versions at the same time?

I'm not sure exactly what you're asking - but i don't think so. As in, if packages in the main repo are updated, this does not automatically mean a release of .DevTools and/or .Typescript, the author seems to keep things seperate in that regard. I can imagine if there are breaking changes all packages of all git repos would be updated.

Would you like me to remove those and then simply refer to the main repo?

[rarkins]

Do these repos all release synchronized versions at the same time?

I'm not sure exactly what you're asking - but i don't think so. As in, if packages in the main repo are updated, this does not automatically mean a release of .DevTools and/or .Typescript, the author seems to keep things seperate in that regard. I can imagine if there are breaking changes all packages of all git repos would be updated.

Would you like me to remove those and then simply refer to the main repo?

If they are from separate repos, and they don't have the same/synchronized versions, then it's not qualified for our "monorepo" grouping. Instead it could be part of group:recommended if you think people usually should update them together at once

[sommmen]

Do these repos all release synchronized versions at the same time?

I'm not sure exactly what you're asking - but i don't think so. As in, if packages in the main repo are updated, this does not automatically mean a release of .DevTools and/or .Typescript, the author seems to keep things seperate in that regard. I can imagine if there are breaking changes all packages of all git repos would be updated.
Would you like me to remove those and then simply refer to the main repo?

If they are from separate repos, and they don't have the same/synchronized versions, then it's not qualified for our "monorepo" grouping. Instead it could be part of group:recommended if you think people usually should update them together at once

I think just having the one monorepo in there is the way to go about things. Updated the PR, hopefully to satisfaction this time. Apologies for the initial wrongful pr.

[renovate-release]

🎉 This PR is included in version 37.200.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.200.0

Your semantic-release bot 📦🚀