Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 1, 2025

Updated Basic.Reference.Assemblies.NetStandard20 from 1.8.0 to 1.8.4.

Release notes

Sourced from Basic.Reference.Assemblies.NetStandard20's releases.

1.8.4

Create release 1.8.4

1.8.3

Create release 1.8.3

1.8.2

Create release 1.8.2

1.8.1

Create release 1.8.1

Commits viewable in compare view.

Updated Microsoft.Build.Locator from 1.11.1 to 1.11.2.

Release notes

Sourced from Microsoft.Build.Locator's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated NATS.Client.Core from 2.5.1 to 2.6.11.

Release notes

Sourced from NATS.Client.Core's releases.

2.6.11

This is a bug fix release of NATS .NET version 2.6.11 with a minor braking change to Object Store models.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.10...v2.6.11

Download from NuGet at https://www.nuget.org/packages/NATS.Net/2.6.11

2.6.10

We're happy to announce support for the new NATS Server version 2.12 features with this NATS .NET release version 2.6.10.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.9...v2.6.10

Download from NuGet https://www.nuget.org/packages/NATS.Net/2.6.10

2.6.9

This is a patch bug fix release version 2.6.9.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.8...v2.6.9

Download Packages

Download this release from NuGet.

2.6.8

Important Bug Fix Release

This is an important bug fix release for Object Store users and JetStream publish behavior. Object store bug was causing object corruption, for example under load or during cluster changes when the JetStream publish request was automatically retried reusing a rented buffer. With this fix we also squashed a JetStream bug where JetStream publish was retrying automatically on a timeout again potentially publishing a message twice.

Object Store Corruption

While putting an object, object store chunks were being retired for publishing to JetStream (Object Store uses JetStream) under certain conditions. When that happened, combined with a buffer management bug, there were cases where object chunks were published twice or with data containing parts of other messages due to mismanagement of rented buffers. Since the meta data was published correctly, the issue was seen when trying to get the object (with any NATS client) as digest mismatch. This avoided using the corrupted objects but they stayed in the stream.

JetStream Double Publish Risk

When publishing to JetStream NATS .NET client automatically retries (twice by default, after 250ms) on receiving a 503 response from the server. However in addition to that the client also retried when receiving no response from the server within two seconds of timeout which potentially publishes messages twice.

See PRs #​937 and #​942 for more details.

Huge thanks to @​MiloszKrajewski for his meticulous analysis and fixing the object store put buffer bug ❤️

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.6.7...v2.6.8

You can download the released packages from NuGet: https://www.nuget.org/packages/NATS.Net/2.6.8

2.6.8-preview.1

This is a bug fix release of NATS .NET version 2.6.8-preview.1.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.7...v2.6.8-preview.1

Download NATS .NET NuGet package using your IDE or the NuGet client.

2.6.7

This is a patch release of NATS .NET client fixing a dispose hang and a consumer bug.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.6...v2.6.7

2.6.6

This is a bug fixes patch release.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.5...v2.6.6

2.6.4

This is a patch release with a few minor features introduced since the last release notes.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.6.1...v2.6.4

2.6.3

Bug fix release for NET Standard 2.0 targets including .NET Framework.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.2-preview.1...v2.6.3

2.6.2-preview.1

Patch release for a new optional feature.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.1...v2.6.2-preview.1

2.6.1

This is mostly a bug fix release of NATS .NET version 2.6.1 with one new feature making it easy to build NatsMsg objects thanks to @​Ivandemidov00. We also refactored some of the reliability features around socket reconnections and consumer error handling.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.0...v2.6.1

2.6.0

We're excited to announce the new NATS .NET v2.6.0 release in time with server v2.11.2 release, with support for Key-Value Store per key TTL feature (thanks to @​stebet). We also various fixes and improvements included in this release.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.16...v2.6.0

2.5.16

We're happy to announce a new NATS .NET release v2.5.16. This release fixes various bugs and introduces a couple of nice features: Socket Connection Factory (enables going through proxies, potentially for other interesting stuff too!) and Direct Request Reply (an internal library improvement). We also want to announce that we have stopped testing against .NET 6.0 although we are still targeting it.

What's Changed

Socket Connection Factory

Thanks to @​wolfkor and @​caleblloyd creating this abstraction, we now have a way of plugging in any implementation that could read and write buffers not just network sockets. Current use case is to enable going through forward proxies but we can't wait to see what other use cases are possible, perhaps can help with testing for example. (#​826, #​828)

public interface INatsSocketConnection : IAsyncDisposable
{
    ValueTask<int> SendAsync(ReadOnlyMemory<byte> buffer);
    ValueTask<int> ReceiveAsync(Memory<byte> buffer);
}

Direct Request Reply

We have received quite a few reports about JetStream publish and other operations timing out under certain scenarios. Even though we suspect at least in some of these cases there maybe a combination of mixing sync and async code leading to thread pool issues and current request reply implementation relying on a single muxed subscription channel potentially creating a bottleneck, we knew there was room for improvement. With this feature (which is not turned on by default) we are by passing the mux subscription channel and delivering replies directly (hence the name) which results in a performance boost of ~10% in response time and about 40% in reducing GC pressure. (#​829)

var opts = new NatsOpts
{
    RequestReplyMode = NatsRequestReplyMode.Direct, // Disabled by default
};
await using var connection = new NatsConnection(opts);

Call for Testing

We invite you to test this new release in your applications with RequestReplyMode set to NatsRequestReplyMode.Direct. We’re particularly interested in feedback from developers who have experienced timeouts related to JetStream publishing.

New Contributors

Full Changelog: nats-io/nats.net@v2.5.15...v2.5.16

Download from NuGet

You can download the latest version from NuGet.

2.5.15

This is a patch release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.14...v2.5.15

Download from NuGet

You can download the latest version from NuGet.

2.5.14

This is a bug fix release.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.12...v2.5.14

Download from NuGet

You can download the latest version from NuGet.

2.5.12

Happy to announce our support for NATS Server 2.11 with this release of NATS .NET version 2.5.12.

What's Changed

  • Add priority group options (overflow) (#​743) @​mtmk

Full Changelog: nats-io/nats.net@v2.5.11...v2.5.12

Support for Other NATS Server 2.11 Features

  • Implement Consumers Pause (#​432) thanks to @​MauriceVanVeen
  • KV TTL support is still in preview and can be found in 2.6 preview releases. thanks to @​stebet
  • You can find the direct batch support in Orbit .NET JetStream Extensions thanks to @​Ivandemidov00

Download from NuGet

You can download the latest version from NuGet.

2.5.11

Minor feature release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.10...v2.5.11

Download from NuGet

You can download the latest version from NuGet.

2.5.10

We're happy to announce a new NATS .NET release v2.5.10. This release includes various bug fixes and minor improvements. Notably, a long standing reconnect bug was fixed with #​758 thanks to @​STARSCrazy's excellent issue report #​750. Also big thanks to @​uhfath for DI improvements with #​757.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.9...v2.5.10

Download from NuGet

You can download the latest version from NuGet.

2.5.9

This is a minor bug fix release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.8...v2.5.9

Download from NuGet

You can download the latest version from NuGet.

2.5.8

We are excited to announce the release of NATS .NET v2.5.8! This version introduces several new features to enhance your experience with the NATS .NET client:

Services: Long-awaited functionality for creating services without queue groups has now been implemented.

KV Store: New Try methods have been added to the KV Store, allowing operations without throwing exceptions. These methods are particularly useful in scenarios where exceptions are not truly exceptional but are used to drive application logic, such as in caching applications. This has been a real community effort. Thanks to everyone involved ❤️

What's Changed

Full Changelog: nats-io/nats.net@v2.5.7...v2.5.8

Download from NuGet

You can download the latest version from NuGet.

2.5.7

We're happy to announce a new NATS .NET release version 2.5.7. This release includes various minor fixes and features. There is also a breaking change in the dependency injection package; please make sure to check the details below.

What's Changed

Breaking Change to NATS.Extensions.Microsoft.DependencyInjection Default Serialization

Since the introduction of INatsClient interface we have made developers and newcomers life easier by providing a sensible default serialization setting that would avoid surprises, and allow ad hoc JSON serialization of custom objects out of the box. With the change Add NatsClient to DI #​689 we are now introducing these defaults into the NATS.Extensions.Microsoft.DependencyInjection package. If you are using this package and want to stay with the old defaults you must change the following options:

  • BoundedChannelFullMode option is applied to the subscription channels and the connection default is to DropNewest. The default applied to the NatsClient instances and in turn to the NATS.Extensions.Microsoft.DependencyInjection package is now to wait when the channel is full. You can set it back to the connection default or if you are happy to go with the new default please make sure to test your application.
  • DefaultSerializerRegistry of NATS.Extensions.Microsoft.DependencyInjection package is the main change with this release, allowing applications to automatically serialize ad hoc objects to JSON, while serializing primitives like byte arrays, numbers, dates, and strings to their raw values using the same serializer registry as NatsClient. We are also deprecating AddJsonSerialization methods to avaoid confusion. They are only marked as Obsolete for now, so there is no need to change that with this release.
services.AddNatsClient(nats =>
{
    // DropNewest was the default, now it's set to Wait. To keep
    // the behavior before this PR add the following line:
    nats.WithSubPendingChannelFullMode(BoundedChannelFullMode.DropNewest);

    // If you were not using custom serializer which doesn't derialize ad hoc JSON
    // objects make sure to add the following to keep to original serializer settings:
    nats.WithSerializerRegistry(NatsDefaultSerializerRegistry.Default);
});

For more information, please check the PR Add NatsClient to DI #​689. Overall, we don't expect many application would be affected by this change; nevertheless, feel free to ask for clarification in the #dotnet channel on http://slack.nats.io if needed.

New Contributors

Full Changelog: nats-io/nats.net@v2.5.6...v2.5.7

NuGet Downloads

https://www.nuget.org/packages/NATS.Net/2.5.7

2.5.6

This is a bug fix release of NATS .NET v2.5.6. It fixes a serialization issue that was happening when interacting with JetStream APIs. Impact should be minimal since JetStream API calls would be retried in most cases however you might see warnings in your logs regarding malformed JSON buffers. The bug was introduced in v2.5.5 and you are strongly encourage to upgrade from v2.5.5. See #​709 for more information.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.5...v2.5.6

Download and Install from NuGet

https://www.nuget.org/packages/NATS.Net

2.5.5

Happy to announce a new release of NATS .NET v2.5.5. With this release we're introducing exception-free methods especially in operations where logic might've been driven by exceptions like the KV get method which might return a not-found. See #​688 for more details.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.4...v2.5.5

https://www.nuget.org/packages/NATS.Net

2.5.3

This is a minor release of a missing feature.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.2...v2.5.3

NuGet

https://www.nuget.org/packages/NATS.Net/2.5.3

2.5.2

Bugfix release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.1...v2.5.2

Commits viewable in compare view.

Updated NATS.Client.JetStream from 2.5.1 to 2.6.11.

Release notes

Sourced from NATS.Client.JetStream's releases.

2.6.11

This is a bug fix release of NATS .NET version 2.6.11 with a minor braking change to Object Store models.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.10...v2.6.11

Download from NuGet at https://www.nuget.org/packages/NATS.Net/2.6.11

2.6.10

We're happy to announce support for the new NATS Server version 2.12 features with this NATS .NET release version 2.6.10.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.9...v2.6.10

Download from NuGet https://www.nuget.org/packages/NATS.Net/2.6.10

2.6.9

This is a patch bug fix release version 2.6.9.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.8...v2.6.9

Download Packages

Download this release from NuGet.

2.6.8

Important Bug Fix Release

This is an important bug fix release for Object Store users and JetStream publish behavior. Object store bug was causing object corruption, for example under load or during cluster changes when the JetStream publish request was automatically retried reusing a rented buffer. With this fix we also squashed a JetStream bug where JetStream publish was retrying automatically on a timeout again potentially publishing a message twice.

Object Store Corruption

While putting an object, object store chunks were being retired for publishing to JetStream (Object Store uses JetStream) under certain conditions. When that happened, combined with a buffer management bug, there were cases where object chunks were published twice or with data containing parts of other messages due to mismanagement of rented buffers. Since the meta data was published correctly, the issue was seen when trying to get the object (with any NATS client) as digest mismatch. This avoided using the corrupted objects but they stayed in the stream.

JetStream Double Publish Risk

When publishing to JetStream NATS .NET client automatically retries (twice by default, after 250ms) on receiving a 503 response from the server. However in addition to that the client also retried when receiving no response from the server within two seconds of timeout which potentially publishes messages twice.

See PRs #​937 and #​942 for more details.

Huge thanks to @​MiloszKrajewski for his meticulous analysis and fixing the object store put buffer bug ❤️

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.6.7...v2.6.8

You can download the released packages from NuGet: https://www.nuget.org/packages/NATS.Net/2.6.8

2.6.8-preview.1

This is a bug fix release of NATS .NET version 2.6.8-preview.1.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.7...v2.6.8-preview.1

Download NATS .NET NuGet package using your IDE or the NuGet client.

2.6.7

This is a patch release of NATS .NET client fixing a dispose hang and a consumer bug.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.6...v2.6.7

2.6.6

This is a bug fixes patch release.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.5...v2.6.6

2.6.4

This is a patch release with a few minor features introduced since the last release notes.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.6.1...v2.6.4

2.6.3

Bug fix release for NET Standard 2.0 targets including .NET Framework.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.2-preview.1...v2.6.3

2.6.2-preview.1

Patch release for a new optional feature.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.1...v2.6.2-preview.1

2.6.1

This is mostly a bug fix release of NATS .NET version 2.6.1 with one new feature making it easy to build NatsMsg objects thanks to @​Ivandemidov00. We also refactored some of the reliability features around socket reconnections and consumer error handling.

What's Changed

Full Changelog: nats-io/nats.net@v2.6.0...v2.6.1

2.6.0

We're excited to announce the new NATS .NET v2.6.0 release in time with server v2.11.2 release, with support for Key-Value Store per key TTL feature (thanks to @​stebet). We also various fixes and improvements included in this release.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.16...v2.6.0

2.5.16

We're happy to announce a new NATS .NET release v2.5.16. This release fixes various bugs and introduces a couple of nice features: Socket Connection Factory (enables going through proxies, potentially for other interesting stuff too!) and Direct Request Reply (an internal library improvement). We also want to announce that we have stopped testing against .NET 6.0 although we are still targeting it.

What's Changed

Socket Connection Factory

Thanks to @​wolfkor and @​caleblloyd creating this abstraction, we now have a way of plugging in any implementation that could read and write buffers not just network sockets. Current use case is to enable going through forward proxies but we can't wait to see what other use cases are possible, perhaps can help with testing for example. (#​826, #​828)

public interface INatsSocketConnection : IAsyncDisposable
{
    ValueTask<int> SendAsync(ReadOnlyMemory<byte> buffer);
    ValueTask<int> ReceiveAsync(Memory<byte> buffer);
}

Direct Request Reply

We have received quite a few reports about JetStream publish and other operations timing out under certain scenarios. Even though we suspect at least in some of these cases there maybe a combination of mixing sync and async code leading to thread pool issues and current request reply implementation relying on a single muxed subscription channel potentially creating a bottleneck, we knew there was room for improvement. With this feature (which is not turned on by default) we are by passing the mux subscription channel and delivering replies directly (hence the name) which results in a performance boost of ~10% in response time and about 40% in reducing GC pressure. (#​829)

var opts = new NatsOpts
{
    RequestReplyMode = NatsRequestReplyMode.Direct, // Disabled by default
};
await using var connection = new NatsConnection(opts);

Call for Testing

We invite you to test this new release in your applications with RequestReplyMode set to NatsRequestReplyMode.Direct. We’re particularly interested in feedback from developers who have experienced timeouts related to JetStream publishing.

New Contributors

Full Changelog: nats-io/nats.net@v2.5.15...v2.5.16

Download from NuGet

You can download the latest version from NuGet.

2.5.15

This is a patch release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.14...v2.5.15

Download from NuGet

You can download the latest version from NuGet.

2.5.14

This is a bug fix release.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.12...v2.5.14

Download from NuGet

You can download the latest version from NuGet.

2.5.12

Happy to announce our support for NATS Server 2.11 with this release of NATS .NET version 2.5.12.

What's Changed

  • Add priority group options (overflow) (#​743) @​mtmk

Full Changelog: nats-io/nats.net@v2.5.11...v2.5.12

Support for Other NATS Server 2.11 Features

  • Implement Consumers Pause (#​432) thanks to @​MauriceVanVeen
  • KV TTL support is still in preview and can be found in 2.6 preview releases. thanks to @​stebet
  • You can find the direct batch support in Orbit .NET JetStream Extensions thanks to @​Ivandemidov00

Download from NuGet

You can download the latest version from NuGet.

2.5.11

Minor feature release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.10...v2.5.11

Download from NuGet

You can download the latest version from NuGet.

2.5.10

We're happy to announce a new NATS .NET release v2.5.10. This release includes various bug fixes and minor improvements. Notably, a long standing reconnect bug was fixed with #​758 thanks to @​STARSCrazy's excellent issue report #​750. Also big thanks to @​uhfath for DI improvements with #​757.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.9...v2.5.10

Download from NuGet

You can download the latest version from NuGet.

2.5.9

This is a minor bug fix release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.8...v2.5.9

Download from NuGet

You can download the latest version from NuGet.

2.5.8

We are excited to announce the release of NATS .NET v2.5.8! This version introduces several new features to enhance your experience with the NATS .NET client:

Services: Long-awaited functionality for creating services without queue groups has now been implemented.

KV Store: New Try methods have been added to the KV Store, allowing operations without throwing exceptions. These methods are particularly useful in scenarios where exceptions are not truly exceptional but are used to drive application logic, such as in caching applications. This has been a real community effort. Thanks to everyone involved ❤️

What's Changed

Full Changelog: nats-io/nats.net@v2.5.7...v2.5.8

Download from NuGet

You can download the latest version from NuGet.

2.5.7

We're happy to announce a new NATS .NET release version 2.5.7. This release includes various minor fixes and features. There is also a breaking change in the dependency injection package; please make sure to check the details below.

What's Changed

Breaking Change to NATS.Extensions.Microsoft.DependencyInjection Default Serialization

Since the introduction of INatsClient interface we have made developers and newcomers life easier by providing a sensible default serialization setting that would avoid surprises, and allow ad hoc JSON serialization of custom objects out of the box. With the change Add NatsClient to DI #​689 we are now introducing these defaults into the NATS.Extensions.Microsoft.DependencyInjection package. If you are using this package and want to stay with the old defaults you must change the following options:

  • BoundedChannelFullMode option is applied to the subscription channels and the connection default is to DropNewest. The default applied to the NatsClient instances and in turn to the NATS.Extensions.Microsoft.DependencyInjection package is now to wait when the channel is full. You can set it back to the connection default or if you are happy to go with the new default please make sure to test your application.
  • DefaultSerializerRegistry of NATS.Extensions.Microsoft.DependencyInjection package is the main change with this release, allowing applications to automatically serialize ad hoc objects to JSON, while serializing primitives like byte arrays, numbers, dates, and strings to their raw values using the same serializer registry as NatsClient. We are also deprecating AddJsonSerialization methods to avaoid confusion. They are only marked as Obsolete for now, so there is no need to change that with this release.
services.AddNatsClient(nats =>
{
    // DropNewest was the default, now it's set to Wait. To keep
    // the behavior before this PR add the following line:
    nats.WithSubPendingChannelFullMode(BoundedChannelFullMode.DropNewest);

    // If you were not using custom serializer which doesn't derialize ad hoc JSON
    // objects make sure to add the following to keep to original serializer settings:
    nats.WithSerializerRegistry(NatsDefaultSerializerRegistry.Default);
});

For more information, please check the PR Add NatsClient to DI #​689. Overall, we don't expect many application would be affected by this change; nevertheless, feel free to ask for clarification in the #dotnet channel on http://slack.nats.io if needed.

New Contributors

Full Changelog: nats-io/nats.net@v2.5.6...v2.5.7

NuGet Downloads

https://www.nuget.org/packages/NATS.Net/2.5.7

2.5.6

This is a bug fix release of NATS .NET v2.5.6. It fixes a serialization issue that was happening when interacting with JetStream APIs. Impact should be minimal since JetStream API calls would be retried in most cases however you might see warnings in your logs regarding malformed JSON buffers. The bug was introduced in v2.5.5 and you are strongly encourage to upgrade from v2.5.5. See #​709 for more information.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.5...v2.5.6

Download and Install from NuGet

https://www.nuget.org/packages/NATS.Net

2.5.5

Happy to announce a new release of NATS .NET v2.5.5. With this release we're introducing exception-free methods especially in operations where logic might've been driven by exceptions like the KV get method which might return a not-found. See #​688 for more details.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.4...v2.5.5

https://www.nuget.org/packages/NATS.Net

2.5.3

This is a minor release of a missing feature.

What's Changed

New Contributors

Full Changelog: nats-io/nats.net@v2.5.2...v2.5.3

NuGet

https://www.nuget.org/packages/NATS.Net/2.5.3

2.5.2

Bugfix release.

What's Changed

Full Changelog: nats-io/nats.net@v2.5.1...v2.5.2

Commits viewable in compare view.

Updated NuGet.Frameworks from 7.0.0 to 7.0.1.

Release notes

Sourced from NuGet.Frameworks's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated NuGet.Versioning from 7.0.0 to 7.0.1.

Release notes

Sourced from NuGet.Versioning's releases.

No release notes found for this version range.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps Basic.Reference.Assemblies.NetStandard20 from 1.8.0 to 1.8.4
Bumps Microsoft.Build.Locator from 1.11.1 to 1.11.2
Bumps NATS.Client.Core from 2.5.1 to 2.6.11
Bumps NATS.Client.JetStream from 2.5.1 to 2.6.11
Bumps NuGet.Frameworks from 7.0.0 to 7.0.1
Bumps NuGet.Versioning from 7.0.0 to 7.0.1

---
updated-dependencies:
- dependency-name: Basic.Reference.Assemblies.NetStandard20
  dependency-version: 1.8.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-all
- dependency-name: Microsoft.Build.Locator
  dependency-version: 1.11.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-all
- dependency-name: NATS.Client.Core
  dependency-version: 2.6.11
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-all
- dependency-name: NATS.Client.JetStream
  dependency-version: 2.6.11
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-all
- dependency-name: NuGet.Frameworks
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-all
- dependency-name: NuGet.Versioning
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-all
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 1, 2025

Labels

The following labels could not be found: dependencies, nuget. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot bot requested a review from ANcpLua as a code owner December 1, 2025 06:25
@github-actions github-actions bot merged commit 45f0de1 into main Dec 1, 2025
14 of 16 checks passed
@github-actions github-actions bot deleted the dependabot/nuget/nuget-all-fa8eb3d0c8 branch December 1, 2025 06:25
@ANcpLua
Copy link
Owner

ANcpLua commented Dec 2, 2025

@claude we dont have any whispermash code as we ditched the idea of our own protocol, remove any leftovers Updated NATS.Client.Core from 2.5.1 to 2.6.11.

Release notes
Updated NATS.Client.JetStream from 2.5.1 to 2.6.11.

@claude
Copy link

claude bot commented Dec 2, 2025

Claude finished @ANcpLua's task —— View jobclaude/pr-66-20251202-0211Create PR ➔


WhisperMesh Removal Complete

All WhisperMesh protocol leftovers have been removed from the codebase.

Summary of changes (30 files changed, -5,408 lines):

  • Removed src/Libraries/WhisperMesh/ library (13 files)
  • Removed tests/Ancplua.Mcp.WhisperMesh.Tests/ test project (5 files)
  • Removed documentation:
    • docs/decisions/ADR-0107-whispermesh-protocol-adoption.md
    • docs/specs/spec-0110-whispermesh-phase1-implementation.md
    • docs/specs/spec-whispermesh-protocol.md
  • Removed NATS.Client.Core and NATS.Client.JetStream from Directory.Packages.props
  • Updated solution file (ancplua-mcp.sln)
  • Cleaned up Workstation server (Program.cs, appsettings.json)
  • Updated CHANGELOG.md with removal notice
  • Removed WhisperAggregatorTools from docs/tool-contracts.md
  • Updated docs/ARCHITECTURE.md (removed WhisperMesh from tree)
  • Removed NATS service from docker-compose.yml
  • Cleaned up Dockerfile.workstation

|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants