We have introduced tx() to support remote transactions with Bytecode based requests in 3.5.0 and 3.5.1 added support for this to Gremlin-Javascript.
In order to also support tx() in .NET, we need to extend the IRemoteConnection interface [1] that providers have to implement if they want to provide their own driver. It needs additional functionality for transactions which results in a breaking change. Given that most providers are not yet on 3.5.x, I wonder whether anyone would actually be affected by this breaking change. Users who implement the interface in tests to get a fake remote connection would also be affected by this, but the required change should be minimal, and we can inform them about this breaking change in the upgrade docs. Overall, it seems worthwhile to accept this breaking change in 3.5.x so we can quickly add the feature for .NET users instead of having to wait for 3.6.0. But we might also be missing something here. So, if anyone has any feedback on this, then please speak up. If there are no objections until next Wednesday (2021-09-15), then I'll assume lazy consensus in favor of accepting the breaking change in the 3.5.x line. The ticket for this is: https://issues.apache.org/jira/browse/TINKERPOP-2556 [1]: https://github.com/apache/tinkerpop/blob/master/gremlin-dotnet/src/Gremlin.N et/Process/Remote/IRemoteConnection.cs
