4.3 Change Log

4.3.2

• Now marks all connections for closure on the expiration of the auth token. This forces the driver to establish new connections and therefore refreshing the credentials. Connections that are currently in use will not be interrupted. An example of this use case would be with LDAP Authentication.

4.3.1

• Fix for the retry mechanism that operates when the client is using transaction functions. Previously the retry was not triggered when an inactive connection was used.

4.3.0

• No changes

4.3.0-rc02

• Fixed a bug where GetRoutingTable procedure was called on protocol versions less than 4.3 using the default access mode which is Write. It is now using Read.

4.3.0-rc01

No changes.

4.3.0-beta1

• Update to ServerInfo object. Deprecating the Version property and replacing it with the new ProtocolVersion property. Added a new property Agent that returns the server agent string

4.3.0-alpha01

• Very first alpha release
• Introduce Bolt Protocol 4.3
• Added net5.0 to target frameworks
• Added dependency on Microsoft.Bcl.AsyncInterfaces so that older c# frameworks can support use of DisposeAsync
• Session objects now implement DisposeAsync so that the await using construct can be used with them rather than having to use try/catch/finally with the finally block closing the session.
• New ROUTE message added to bolt protocol which replaces the use of dbms.cluster.routing.getRoutingTable when the driver requests a routing table update.
• Implemented extended handshake on bolt protocol. Now supports a major version and range, where as previously it just supported four specific versions.
• Introduction of Testkit. Implemented .net backend to support this.