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 to Rust 1.72 #20258

Merged
merged 3 commits into from
Aug 27, 2023
Merged

chore: update to Rust 1.72 #20258

merged 3 commits into from
Aug 27, 2023

Conversation

linbingquan
Copy link
Contributor

As the title.

@bartlomieju bartlomieju added this to the 1.37 milestone Aug 24, 2023
@mmastrac
Copy link
Contributor

Looks go to me to land for the next minor release.

@linbingquan linbingquan marked this pull request as ready for review August 25, 2023 03:04
@linbingquan
Copy link
Contributor Author

@mmastrac I don't know why it can't pass the test in ubuntu.

https://github.com/denoland/deno/actions/runs/5971650008/job/16201009951?pr=20258

@mmastrac
Copy link
Contributor

@linbingquan Please try bumping the version of async-trait to 1.1.73 in Cargo.toml to fix that lint issue.

@mmastrac mmastrac merged commit 2080669 into denoland:main Aug 27, 2023
12 checks passed
@linbingquan linbingquan deleted the dev-rust branch August 27, 2023 04:25
bartlomieju pushed a commit that referenced this pull request Aug 31, 2023
<!--
Before submitting a PR, please read https://deno.com/manual/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't
run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench'
label.
-->

As the title.

---------

Co-authored-by: Matt Mastracci <[email protected]>
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.

3 participants