chore(versionable): prepare release 0.2.0

Author: nsarlin-zama

tfhe/Cargo.toml

@@ -79,7 +79,7 @@ sha3 = { version = "0.10", optional = true }
 itertools = "0.11.0"
 rand_core = { version = "0.6.4", features = ["std"] }
 tfhe-zk-pok = { version = "0.2.0", path = "../tfhe-zk-pok", optional = true }
-tfhe-versionable = { version = "0.1.0", path = "../utils/tfhe-versionable" }
+tfhe-versionable = { version = "0.2.0", path = "../utils/tfhe-versionable" }
 
 # wasm deps
 wasm-bindgen = { version = "0.2.86", features = [

tfhe/docs/guides/data_versioning.md

@@ -17,7 +17,7 @@ You can load serialized data with the `unversionize` function, even in newer ver
 [dependencies]
 # ...
 tfhe = { version = "0.8.0", features = ["integer","x86_64-unix"]}
-tfhe-versionable = "0.1.0"
+tfhe-versionable = "0.2.0"
 bincode = "1.3.3"
 ```
 

utils/tfhe-versionable-derive/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tfhe-versionable-derive"
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 keywords = ["versioning", "serialization", "encoding", "proc-macro", "derive"]
 homepage = "https://zama.ai/"

utils/tfhe-versionable/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "tfhe-versionable"
-version = "0.1.0"
+version = "0.2.0"
 edition = "2021"
 keywords = ["versioning", "serialization", "encoding"]
 homepage = "https://zama.ai/"
@@ -26,6 +26,6 @@ toml = "0.8"
 
 [dependencies]
 serde = { version = "1.0", features = ["derive"] }
-tfhe-versionable-derive = { version = "0.1.0", path = "../tfhe-versionable-derive" }
+tfhe-versionable-derive = { version = "0.2.0", path = "../tfhe-versionable-derive" }
 num-complex = { version = "0.4", features = ["serde"] }
 aligned-vec = { version = "0.5", features = ["serde"] }

utils/tfhe-versionable/README.md

@@ -1,6 +1,6 @@
 # TFHE-versionable
 This crate provides type level versioning for serialized data. It offers a way to add backward
-compatibility on any data type. The versioning scheme works recursively and is idependant of the
+compatibility on any data type. The versioning scheme works recursively and is independant of the
 chosen serialization backend.
 
 To use it, simply define an enum that have a variant for each version of your target type.