-
Notifications
You must be signed in to change notification settings - Fork 71
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
Cargo.lock: Update rustix and bitflags dependencies to latest version #741
Cargo.lock: Update rustix and bitflags dependencies to latest version #741
Conversation
Update rustix dependency to its latest version and fix it on: * Cargo.lock * e2e_tests/Cargo.lock * fuzz/Cargo.lock Signed-off-by: Tomás González <[email protected]>
* Keep rustix updated and avoid a dependency mismatch with parsec-tool. * Update Cargo.lock, e2e_tests/Cargo.lock, fuzz/Cargo.lock Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
@@ -156,9 +156,9 @@ checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a" | |||
|
|||
[[package]] | |||
name = "bitflags" | |||
version = "2.4.0" |
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.
Sorry I didn't understand the commit description
* Keep rustix updated and avoid a dependency mismatch with
parsec-tool.
Will the bitflags crate have different versions in parsec and parsec-tool if we update rustix?
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.
https://github.com/tgonzalezorlandoarm/parsec-tool/actions/runs/6972139517/job/18973702435
When checking the current mismatches between parsec and parsec-tool:
---------------------mistmatches----------------------
bitflags ['v2.4.1', 'v2.4.0']
rustix ['v0.38.18', 'v0.38.21']
As dependabot pointed out, rustix can be updated to its latest. So can bitflags. This PR is doing that.
This is done in parsec-tool as well as part of this parallaxsecond/parsec-tool#116
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.
This will avoid a dependency mismatch between parsec and parsec-tool
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.
LGTM
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.
LGTM
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec. Please check: parallaxsecond/parsec#741 Signed-off-by: Tomás González <[email protected]>
Update rustix dependency to its latest version and fix it on:
This has been marked by dependabot in different PRs: