v3.0.0

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 Entries are listed in reverse chronological order.
 
+# 3.0.0
+
+* Fix typo by @rex4539 in https://github.com/ZcashFoundation/ed25519-zebra/pull/32
+* Add Zeroize impl for SigningKey by @kim in https://github.com/ZcashFoundation/ed25519-zebra/pull/34
+* Add JNI code for ed25519-zebra by @droark in https://github.com/ZcashFoundation/ed25519-zebra/pull/37
+* Update rand_core to 0.6 and rand to 0.8 by @dconnolly in https://github.com/ZcashFoundation/ed25519-zebra/pull/44
+* dependencies: update zeroize to 1.2 by @FintanH in https://github.com/ZcashFoundation/ed25519-zebra/pull/52
+
 # 2.2.0
 
 * Add `PartialOrd`, `Ord` implementations for `VerificationKeyBytes`.  While

Cargo.toml

@@ -2,8 +2,7 @@
 name = "ed25519-zebra"
 # Before publishing:
 # - update CHANGELOG.md
-# - update html_root_url
-version = "2.2.0"
+version = "3.0.0"
 authors = ["Henry de Valence <hdevalence@hdevalence.ca>"]
 license = "MIT OR Apache-2.0"
 edition = "2018"

README.md

@@ -20,10 +20,10 @@ matching the Zcash consensus rules exactly.
 However, this library may be of independent interest, as it implements
 ZIP215, a set of precisely specified validation rules for Ed25519 that make
 individual verification consistent with batch verification and are
-backwards-compatible with all existing Ed25519 signatures. Any non-Zcash users 
+backwards-compatible with all existing Ed25519 signatures. Any non-Zcash users
 should use the ZIP215 rules:
 ```toml
-ed25519-zebra = "2"
+ed25519-zebra = "3"
 ```
 
 ## ZIP 215 and changes to Zcash-flavored Ed25519
@@ -36,12 +36,12 @@ dependence on validation rules inherited from a specific point release of
 verification. More details and motivation are available in the text of [ZIP215].
 
 The `1.x` series of this crate implements the legacy, pre-ZIP-215 validation
-criteria; the `2.x` series of this crate implements the post-ZIP-215
+criteria; the `2.x+` series of this crate implements the post-ZIP-215
 validation criteria.  Users (like Zebra or zcashd) who need to handle the
 upgrade can use both versions simultaneously using cargo renaming, e.g.,
 ```toml
 ed25519-zebra-legacy = { package = "ed25519-zebra", version = "1" }
-ed25519-zebra-zip215 = { package = "ed25519-zebra", version = "2" }
+ed25519-zebra-zip215 = { package = "ed25519-zebra", version = "3" }
 ```
 
 ## Example

ed25519jni/rust/Cargo.toml

@@ -1,13 +1,13 @@
 [package]
 name = "ed25519jni"
-version = "0.0.4-JNI-DEV"
+version = "0.0.5-JNI-DEV"
 authors = ["Douglas Roark <douglas.roark@gemini.com>"]
 license = "MIT OR Apache-2.0"
 publish = false
 edition = "2018"
 
 [dependencies]
-ed25519-zebra = { path = "../../", version = "2.2.0" }
+ed25519-zebra = { path = "../../", version = "3.0.0" }
 failure = "0.1.8"
 jni = "0.18.0"