1.7 changelog

v1.7.0-alpha4

• Removed master branch and made 1.7 the default which will hold the long run stable 1.7 driver release (the same applies to downstream - gobolt and seabolt).
• Renamed seabolt wrapper from neo4j-go-connector to gobolt (accessible at https://github.com/neo4j-drivers/gobolt)
• Changed the package structure of the driver as per packaging guidelines and moved top level code into neo4j folder which can now be imported from github.com/neo4j/neo4j-go-driver/neo4j
• Made the logger provided to the driver through neo4j.Config to be used across the whole stack (now you can get more useful log entries from seabolt - especially when DEBUG log level is enabled)
• Added support for bolt+routing scheme to work against causal cluster deployments, yay! (all you need to do is to point your URL to bolt+routing://<hostname>:<port> where <hostname>:<port> pair points to one of the core servers in the cluster)
• Added support for specifying custom neo4j.ServerAddressResolver through neo4j.Config that can map <hostname>:<port> pair provided as part of the driver URL to multiple entries (i.e to provide all core server addresses) - so that all those mapped entries are tried in turn until routing table is fetched
• Renamed spatial type constructor function neo4j.NewPoint to neo4j.NewPoint2D for consistency
• Enabled SNI extension on TLS sessions

v1.7.0-alpha3

• Added support for all temporal and spatial types that were introduced by Bolt version 2 (introduced as part of server release 3.4)
• Added support for returning Path types as return values

v1.7.0-alpha2

• Fixed an issue where node and relationship values returned from a query was not accessible through driver

v1.7.0-alpha1

• The first release of the Neo4j Official Go Driver. It only includes support for Bolt V1 (which means you cannot use temporal / spatial types introduced with Neo4j database 3.4 version) and works only on direct mode (no clustering support)