chore: release v4.1.1

BEagle1984 · Feb 26, 2023 · ce93478 · ce93478
1 parent 5fb0771
commit ce93478
Show file tree

Hide file tree

Showing 4 changed files with 2 additions and 73 deletions.
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -1,6 +1,6 @@
 <Project>
   <PropertyGroup Label="Package information">
-    <BaseVersionSuffix>-beta.1</BaseVersionSuffix>
+    <BaseVersionSuffix></BaseVersionSuffix>
     <BaseVersion>4.1.1$(BaseVersionSuffix)</BaseVersion>
     <DatabasePackagesRevision>1</DatabasePackagesRevision>
     <DatabasePackagesVersionSuffix>$(BaseVersionSuffix)</DatabasePackagesVersionSuffix>

diff --git a/docs/concepts/broker/testing.md b/docs/concepts/broker/testing.md
@@ -220,8 +220,7 @@ public class IntegrationTests : IClassFixture<WebApplicationFactory<Startup>>
 
 Many aspects of the Kafka broker have been mocked to replicated as much as possible the behavior you have when connected with the real broker. This new implementation supports commits, kafka events, offset reset, partitioning, rebalance, etc.
 
-The implementation revolves around the <xref:Silverback.Messaging.Broker.Kafka.Mocks.IInMemoryTopicCollection>. This type is registered as singleton and can be resolved in the tests to gain access to the <xref:Silverback.Messaging.Broker.Kafka.Mocks.IInMemoryTopic> instances directly and inspect their partitions, offsets, etc.
-Alternatively the <xref:Silverback.Messaging.Broker.Kafka.Mocks.IInMemoryTopic> can be retrieved via the `GetTopic` method of the <xref:Silverback.Testing.IKafkaTestingHelper>.
+The mocked topics can be retrieved and inspected via the `GetTopic` method of the <xref:Silverback.Testing.IKafkaTestingHelper>.
 
 ### Partitioning
 

diff --git a/src/Silverback.Storage.Memory/Silverback.Storage.Memory.csproj b/src/Silverback.Storage.Memory/Silverback.Storage.Memory.csproj
diff --git a/src/Silverback.Storage.Sqlite/Silverback.Storage.Sqlite.csproj b/src/Silverback.Storage.Sqlite/Silverback.Storage.Sqlite.csproj