chore: fix yanked bytes #4517
Merged
chore: fix yanked bytes #4517
Conversation
This file contains 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
eval-exec
approved these changes
Jul 15, 2024
Merged
via the queue into
nervosnetwork:develop
with commit Jul 15, 2024
b962885
31 of 32 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem does this PR solve?
error[yanked]: detected yanked crate (try `cargo update -p bytes`) ┌─ /home/runner/work/ckb/ckb/Cargo.lock:40:1 │ 40 │ bytes 1.6.0 registry+https://github.com/rust-lang/crates.io-index │ ----------------------------------------------------------------- yanked versionWhat is changed and how it works?
Upgrade bytes to >=4.1.3
Check List
Tests
Release note