Skip to content

deps(deps): bump ed25519-dalek from 2.2.0 to 3.0.0 #11064

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 2 commits into from
+82 −25
Closed

deps(deps): bump ed25519-dalek from 2.2.0 to 3.0.0 #11064

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
23968a6
deps(deps): bump ed25519-dalek from 2.2.0 to 3.0.0
dependabot[bot] Sep 22, 2026
cb284e2
docs: add changelog fragment for #11064
Sep 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
90 changes: 68 additions & 22 deletions Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

11 changes: 11 additions & 0 deletions changelog.d/11064-ed25519-dalek-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
Bumped `ed25519-dalek` 2.2.0 → 3.0.0 (dependabot) in `perry`, `perry-stdlib`, and
`perry-updater`. The major bump pulls in `curve25519-dalek` 5.0.0, `sha2` 0.11.0,
`rand_core` 0.10.1, and a matching `ed25519` 3.0.0, but leaves the surface Perry
actually touches unchanged: `SigningKey`/`VerifyingKey::from_bytes`,
`Signature::from_bytes`/`try_from`, and the `Signer`/`Verifier` trait methods
used in `crates/perry-stdlib/src/crypto/`, `crates/perry-stdlib/src/webcrypto/`,
`crates/perry-updater/src/{cli_manifest,core}.rs`, and
`crates/perry/src/commands/updater.rs` all kept their existing signatures, so
none of those call sites needed to change. `jsonwebtoken` (an indirect,
optional-feature consumer) stays pinned on `ed25519-dalek` 2.2.0, so both major
versions coexist in the lockfile without conflict.
2 changes: 1 addition & 1 deletion crates/perry-stdlib/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -385,7 +385,7 @@ argon2 = { version = "0.5", optional = true }
base64 = { workspace = true, optional = true }
x25519-dalek = { version = "2.0", features = ["static_secrets"], optional = true }
x448 = { version = "0.14.0-pre.9", features = ["static_secrets"], optional = true }
ed25519-dalek = { version = "2.1", optional = true }
ed25519-dalek = { version = "3.0", optional = true }
ed448-goldilocks = { version = "0.14.0-pre.13", default-features = false, features = ["alloc", "signing"], optional = true }
aes-gcm = { version = "0.10", optional = true }
chacha20poly1305 = { version = "0.10", optional = true }
Expand Down
2 changes: 1 addition & 1 deletion crates/perry-updater/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ semver.workspace = true
sha2 = "0.11"
hex.workspace = true
base64.workspace = true
ed25519-dalek = "2.1"
ed25519-dalek = "3.0"

[dev-dependencies]
tempfile.workspace = true
Expand Down
2 changes: 1 addition & 1 deletion crates/perry/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@ fslock = "0.2"
# feature — listing them as direct deps just makes them callable from
# the CLI module. ed25519-dalek 2.1 takes any CryptoRng; we use rand 0.9
# for the keygen seed.
ed25519-dalek = { version = "2.1", features = ["rand_core"], optional = true }
ed25519-dalek = { version = "3.0", features = ["rand_core"], optional = true }
sha2 = "0.11"
hex.workspace = true
rand = { version = "0.10", optional = true }
Expand Down
Loading