Skip to content

Commit 59efca3

Browse files
committed
chore: bump tfhe to 1.0.0
1 parent e19f210 commit 59efca3

File tree

12 files changed

+15
-15
lines changed

12 files changed

+15
-15
lines changed

tfhe/Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
name = "tfhe"
3-
version = "0.11.0"
3+
version = "1.0.0"
44
edition = "2021"
55
readme = "../README.md"
66
keywords = ["fully", "homomorphic", "encryption", "fhe", "cryptography"]

tfhe/docs/fundamentals/serialization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ In the following example, we use [bincode](https://crates.io/crates/bincode) for
158158

159159
[dependencies]
160160
# ...
161-
tfhe = { version = "0.11.0", features = ["integer"] }
161+
tfhe = { version = "1.0.0", features = ["integer"] }
162162
bincode = "1.3.3"
163163
```
164164

tfhe/docs/getting_started/benchmarks/summary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ This document summarizes the timings of some homomorphic operations over 64-bit
44

55
The cryptographic parameters used for benchmarking follow a tweaked uniform (TUniform) noise distribution instead of a Gaussian. The main advantage of this distribution is to be bounded, whereas the usual Gaussian one is not. In some practical cases, this can simplify the use of homomorphic computation. See the [noise section](../security\_and\_cryptography.md#noise) of the Security and cryptography documentation page for more information on the noise distributions.
66

7-
You can get the parameters used for benchmarks by cloning the repository and checking out the commit you want to use (starting with the v0.11.0 release) and run the following make command:
7+
You can get the parameters used for benchmarks by cloning the repository and checking out the commit you want to use (starting with the v1.0.0 release) and run the following make command:
88

99
```console
1010
make print_doc_bench_parameters

tfhe/docs/getting_started/installation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This document provides instructions to set up **TFHE-rs** in your project.
77
First, add **TFHE-rs** as a dependency in your `Cargo.toml`.
88

99
```toml
10-
tfhe = { version = "0.11.0", features = ["boolean", "shortint", "integer"] }
10+
tfhe = { version = "1.0.0", features = ["boolean", "shortint", "integer"] }
1111
```
1212

1313
{% hint style="info" %}
@@ -35,5 +35,5 @@ By default, **TFHE-rs** makes the assumption that hardware AES features are enab
3535
To add support for older CPU, import **TFHE-rs** with the `software-prng` feature in your `Cargo.toml`:
3636

3737
```toml
38-
tfhe = { version = "0.11.0", features = ["boolean", "shortint", "integer", "software-prng"] }
38+
tfhe = { version = "1.0.0", features = ["boolean", "shortint", "integer", "software-prng"] }
3939
```

tfhe/docs/getting_started/quick_start.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ edition = "2021"
5959
Then add the following configuration to include **TFHE-rs**:
6060

6161
```toml
62-
tfhe = { version = "0.11.0", features = ["integer"] }
62+
tfhe = { version = "1.0.0", features = ["integer"] }
6363
```
6464

6565
Your updated `Cargo.toml` file should look like this:
@@ -71,7 +71,7 @@ version = "0.1.0"
7171
edition = "2021"
7272

7373
[dependencies]
74-
tfhe = { version = "0.11.0", features = ["integer"] }
74+
tfhe = { version = "1.0.0", features = ["integer"] }
7575
```
7676

7777
If you are on a different platform please refer to the [installation documentation](installation.md) for configuration options of other supported platforms.

tfhe/docs/guides/array.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The following example shows a complete workflow of working with encrypted arrays
1919
# Cargo.toml
2020

2121
[dependencies]
22-
tfhe = { version = "0.11.0", features = ["integer"] }
22+
tfhe = { version = "1.0.0", features = ["integer"] }
2323
```
2424

2525
```rust

tfhe/docs/guides/data_versioning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can load serialized data with the `unversionize` function, even in newer ver
1616

1717
[dependencies]
1818
# ...
19-
tfhe = { version = "0.11.0", features = ["integer"] }
19+
tfhe = { version = "1.0.0", features = ["integer"] }
2020
tfhe-versionable = "0.4.0"
2121
bincode = "1.3.3"
2222
```

tfhe/docs/guides/run_on_gpu.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To use the **TFHE-rs** GPU backend in your project, add the following dependency
1919

2020

2121
```toml
22-
tfhe = { version = "0.11.0", features = ["boolean", "shortint", "integer", "gpu"] }
22+
tfhe = { version = "1.0.0", features = ["boolean", "shortint", "integer", "gpu"] }
2323
```
2424

2525
{% hint style="success" %}

tfhe/docs/guides/strings.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Here is an example:
2929
# Cargo.toml
3030

3131
[dependencies]
32-
tfhe = { version = "0.11.0", features = ["integer", "strings"] }
32+
tfhe = { version = "1.0.0", features = ["integer", "strings"] }
3333
```
3434

3535
```rust

tfhe/docs/references/core-crypto-api/tutorial.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Welcome to this tutorial about `TFHE-rs` `core_crypto` module.
99
To use `TFHE-rs`, it first has to be added as a dependency in the `Cargo.toml`:
1010

1111
```toml
12-
tfhe = { version = "0.11.0" }
12+
tfhe = { version = "1.0.0" }
1313
```
1414

1515
### Commented code to double a 2-bit message in a leveled fashion and using a PBS with the `core_crypto` module.

0 commit comments

Comments
 (0)