chore(deps): bump ed25519-dalek from 2.2.0 to 3.0.0#643
Merged
Conversation
Bumps [ed25519-dalek](https://github.com/dalek-cryptography/curve25519-dalek) from 2.2.0 to 3.0.0. - [Release notes](https://github.com/dalek-cryptography/curve25519-dalek/releases) - [Changelog](https://github.com/dalek-cryptography/curve25519-dalek/blob/3.0.0/CHANGELOG.md) - [Commits](dalek-cryptography/curve25519-dalek@ed25519-2.2.0...3.0.0) --- updated-dependencies: - dependency-name: ed25519-dalek dependency-version: 3.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Collaborator
Author
|
Closing as redundant — the identical fix (ed25519-dalek 2.2.0→3.0.0, same rebase-off-a-fresh-branch approach) was independently completed and merged via #568 a few minutes ago. This branch is now a no-op against |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ed25519-dalekfrom 2.2.0 to 3.0.0 incrates/traverse-runtime/Cargo.toml. That branch had accumulated a real merge conflict againstmain(Cargo.lockandcrates/traverse-runtime/Cargo.toml, from unrelated dependency/feature changes landing onmainsince the PR opened), so this reopens it from a fresh branch rather than rewriting the bot-owned branch's history.main, resolved the two-file conflict (keptmain's other in-flight dependency versions —sha2 = "0.11",zeroize, optionalwasmtime/wasmtime-wasi,uuidwith thejsfeature — and tooked25519-dalek = "3.0.0"from the dependabot side), then regeneratedCargo.lockviacargo update -p ed25519-dalekrather than hand-editing lockfile conflict markers. Original dependabot commit authorship preserved.traverse-clihas its own separateed25519-dalek = "2.2.0"dependency, untouched — out of scope for this bump (dependabot only targetedtraverse-runtime's usage).Governing Spec
ed25519-dalekis used incrates/traverse-runtime/src/security.rsfor signing/verification under this spec; version-bump only, no behavioral or API change intraverse-runtime's own code.Project Item
N/A — dependency bump, not tracked against a Project 1 issue.
Validation
cargo build --workspace— cleancargo test --workspace— all green, zero failurescargo clippy --workspace --all-targets -- -D warnings— cleancargo fmt --check— clean🤖 Generated with Claude Code