-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
chore: update reqwest, object-store #18789
Conversation
@bmwill is attempting to deploy a commit to the Mysten Labs Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
You are brave @bmwill! I started doing the same with hyper, axum, and http and started pulling white hairs soon after 🦀 |
I am slightly worried about upgrading to a new |
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.
Thanks @bmwill
## Description Pick PRs to introduce the `ConsensusCommitPrologueV3` types into the (soon-to-be legacy) GraphQL release branch, so that it can continue deserializing transaction blocks and effects. Cherry picks include: #17678, #18816, #18789 (+ a pick to `fastcrypto` to use `reqwest 0.12`). ## Test plan ``` sui$ cargo simtest sui-graphql-rpc$ cargo nextest run sui-graphql-e2e-tests$ cargo nextest run --features pg_integration ``` and CI --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK: - [ ] REST API: --------- Co-authored-by: Brandon Williams <[email protected]>
Update a number of http related libraries, including but not limited to:
A future PR will continue by upgrading anemo, rustls, hyper
Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.