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.
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.
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
deps(identity): update ed25519-dalek to 2.0 #4337
deps(identity): update ed25519-dalek to 2.0 #4337
Changes from 6 commits
015c28c
cd37165
abbcea9
0555126
3449fee
de50a75
bfbeffe
6c6d653
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a bump of
libp2p-identity
in the rootCargo.toml
. See CI failure: https://github.com/libp2p/rust-libp2p/actions/runs/5891817364/job/15979771326?pr=4337There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I tried it, but if I do it all other
semver-check
workflows fail, see hereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe cargo-semver-check does not adhere to the override?
rust-libp2p/Cargo.toml
Lines 111 to 118 in cbdbaa8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am surprised that this is showing up now, how did we ever bump this version? Maybe this failure happens now with the recent version change of
cargo semver-checks
?The issue with
libp2p-identity
is that we need to patch it across the workspace and I'd assume that the temporary workspace created bycargo semver-checks
does not support that. To properly fix this, we should movelibp2p-identity
out of the mono-repo. We should very rarely make breaking changes to it anyway because it sits at the very bottom of the dependency chain of the ecosystem.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe @obi1kenobi you have seen this issue before, i.e. that
cargo-semver-checks
does not adhere to the workspacepatch
es. Note that this is only a suspicion. Issue might as well be on the rust-libp2p end.@thomaseizinger @jxs I am fine merging here as is, i.e. with the failing
cargo-semver-checks
check on thelibp2p-identity
run. Oncelibp2p-identity
v0.2.3
is released we can update our rootCargo.toml
. Objections?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I don't believe it copies patches. You can double-check and make sure by looking up the generated manifest inside
target/semver-checks
. But I'm pretty sure we never read patches from the source manifest so that's probably it.If running
cargo-semver-checks
on an intermediate state that isn't right before acargo publish
, checking with patches included makes sense.But is there risk that pre-publish checking while using patches might falsely say there are no semver issues, only for issues to come up after the crate gets published and used by users that don't have the patches locally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated main
Cargo.toml
toidentity
0.2.3