Update the changelog and readme

Author: matthewmcneely

CHANGELOG.md

@@ -5,6 +5,22 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project
 adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+## Unreleased
+
+**Added**
+
+- Add v25 Dgraph API
+  - Added new `run_dql()` method for executing DQL queries directly
+  - Added `allocate_uids()` method for allocating unique identifiers
+  - Added `allocate_timestamps()` method for allocating timestamps
+  - Added `allocate_namespaces()` method for allocating namespace IDs
+  - Added namespace management methods:
+    - `create_namespace()` - Creates a new namespace and returns its ID
+    - `drop_namespace()` - Drops the specified namespace
+    - `list_namespaces()` - Lists all available namespaces
+  - Updated proto definitions to support Dgraph v25 API
+  - Enhanced client functionality with new gRPC service methods
+
 ## [v24.3.0] - 2025-07-29
 
 **Chore**

README.md

@@ -101,6 +101,7 @@ Valid connection string args:
 | apikey      | \<key\>                         | a Dgraph Cloud API Key                                                                                                                                        |
 | bearertoken | \<token\>                       | an access token                                                                                                                                               |
 | sslmode     | disable \| require \| verify-ca | TLS option, the default is `disable`. If `verify-ca` is set, the TLS certificate configured in the Dgraph cluster must be from a valid certificate authority. |
+| namespace   | \<namespace\>                   | a previously created integer-based namespace, username and password must be supplied                                                                          |
 
 Note the `sslmode=require` pair is not supported and will throw an Exception if used. Python grpc
 does not support traffic over TLS that does not fully verify the certificate and domain. Developers
@@ -115,6 +116,7 @@ Some example connection strings:
 | dgraph://sally:supersecret@dg.example.com:443?sslmode=verify-ca                                              | Connect to remote server, use ACL and require TLS and a valid certificate from a CA |
 | dgraph://foo-bar.grpc.us-west-2.aws.cloud.dgraph.io:443?sslmode=verify-ca&apikey=\<your-api-connection-key\> | Connect to a Dgraph Cloud cluster                                                   |
 | dgraph://foo-bar.grpc.hypermode.com:443?sslmode=verify-ca&bearertoken=\<some access token\>                  | Connect to a Dgraph cluster protected by a secure gateway                           |
+| dgraph://sally:supersecret@dg.example.com:443?namespace=2                                                    | Connect to a ACL enabled Dgraph cluster in namespace 2                              |
 
 Using the `Open` function with a connection string: