You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,34 @@
1
+
#### 1.5.32 December 23rd 2024 ####
2
+
3
+
*[Bump Akka.NET to 1.5.32](https://github.com/akkadotnet/akka.net/releases/tag/1.5.32)
4
+
*[Bump Akka.Persistence.Hosting to 1.5.32](https://github.com/akkadotnet/Akka.Hosting/releases/tag/1.5.32)
5
+
*[Bump MongoDB.Driver to 3.0.0](https://github.com/akkadotnet/Akka.Persistence.MongoDB/pull/395)
6
+
7
+
**Breaking Change Notice**
8
+
9
+
Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases **WILL NOT** support:
10
+
* MongoDb server v3.6 and earlier
11
+
* Projects that targets .NET Core 2.x and lower
12
+
* Projects that targets .NET Framework 2.7.1 and lower
13
+
* LINQ2 provider
14
+
* TLS 1.0 and 1.1
15
+
16
+
**Driver Behavior Change And Workaround**
17
+
18
+
There is a behavior change in `MongoDb.Driver` v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.
19
+
20
+
Example:
21
+
* Server address used in connection string: "host.docker.internal:27017"
22
+
* Actual server address being used in MongoDb connection: "127.0.0.1:27017"
23
+
24
+
The workaround is to add "directConnection=true" in your connection string.
0 commit comments