Prepare for the release

Signed-off-by: Hugues de Valon <[email protected]>

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "parsec-client"
-version = "0.12.0"
+version = "0.13.0"
 authors = ["Contributors to the Parsec project"]
 description = "Parsec Client library for the Rust ecosystem"
 license = "Apache-2.0"
@@ -12,7 +12,7 @@ edition = "2018"
 documentation = "https://docs.rs/crate/parsec-client"
 
 [dependencies]
-parsec-interface = { git = "https://github.com/parallaxsecond/parsec-interface-rs.git", rev = "6b951390791b398b76eb02c942e24d7c91acc980"}
+parsec-interface = "0.25.0"
 num = "0.3.0"
 log = "0.4.11"
 derivative = "2.1.1"

README.md

@@ -10,12 +10,17 @@ This repository contains a Rust client for consuming the API provided by the [Pa
 The low-level functionality that this library uses for IPC is implemented in the [interface crate](https://github.com/parallaxsecond/parsec-interface-rs).
 
 When using the JWT-SVID authentication method, the client will expect the `SPIFFE_ENDPOINT_SOCKET` environment variable to contain the path of the Workload API endpoint.
+You will need to compile the crate with the `spiffe-auth` feature activated.
 See the [SPIFFE Workload Endpoint](https://github.com/spiffe/spiffe/blob/master/standards/SPIFFE_Workload_Endpoint.md#4-locating-the-endpoint) for more information.
 
 ## Locating the Parsec endpoint
 
 The Rust client follows the [service discovery](https://parallaxsecond.github.io/parsec-book/parsec_client/api_overview.html#service-discovery) policy
-to find the Parsec endpoint.
+to find the Parsec endpoint. For example if the socket is at `/tmp/parsec.sock`:
+
+```
+export PARSEC_SERVICE_ENDPOINT="unix:/tmp/parsec.sock"
+```
 
 ## License