Skip to content
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 tokio to 1.28 #9023

Merged
merged 2 commits into from
May 8, 2023
Merged

chore: update tokio to 1.28 #9023

merged 2 commits into from
May 8, 2023

Conversation

miraclx
Copy link
Contributor

@miraclx miraclx commented May 8, 2023

Audits in near-sdk highlight a security vulnerability RUSTSEC-2023-0001 that affects the Windows platform.

As far as I could tell, we're not directly impacted by this, but the severity suggests we make an upstream dep update.

#8309 (comment) pinned tokio to 1.18 and suggested not updating the minor version unconsciously. Whereas #8472 required a bump to 1.19, which has no versions that patch this vulnerability.

This PR seizes the opportunity to re-pin the minor version to the latest, after which subsequent updates can uphold the bump requirement outlined in #8309.

@miraclx miraclx requested a review from a team as a code owner May 8, 2023 05:17
@miraclx miraclx requested a review from mzhangmzz May 8, 2023 05:17
@miraclx miraclx changed the title chore: update tokio chore: update tokio to 1.28 May 8, 2023
@near-bulldozer near-bulldozer bot merged commit 3a46933 into master May 8, 2023
@near-bulldozer near-bulldozer bot deleted the miraclx/update-tokio branch May 8, 2023 17:05
nikurt pushed a commit that referenced this pull request May 10, 2023
[Audits](https://github.com/near/near-sdk-rs/actions/runs/4690517670/jobs/8376852068?pr=1010) in `near-sdk` highlight a security vulnerability [RUSTSEC-2023-0001](https://rustsec.org/advisories/RUSTSEC-2023-0001) that affects the Windows platform.

As far as I could tell, we're not directly impacted by this, but the severity suggests we make an upstream dep update.

#8309 (comment) pinned `tokio` to `1.18` and suggested not updating the minor version unconsciously. Whereas #8472 required a bump to `1.19`, which has no versions that patch this vulnerability.

This PR seizes the opportunity to re-pin the minor version to the latest, after which subsequent updates can uphold the bump requirement outlined in #8309.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants