Skip to content

Commit

Permalink
chore: bump MSRV to 1.56 (#2546)
Browse files Browse the repository at this point in the history
As part of upgrading syn to 2.0 (e.g.,
#2516), we need to bump the MSRV
to 1.56. As part of this PR, I've:
- Updated the text descriptions of what would be an in-policy MSRV bump
  to use more recent versions of rustc. The _niceness_ of said version
  numbers are purely coincidental.
- I've removed some of the exceptions made in CI.yml in order to support
  some crates with a higher MSRV.
  • Loading branch information
davidbarsky committed Sep 26, 2023
1 parent bd589c2 commit 887efb9
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions tracing-mock/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ structured, event-based diagnostic information. `tracing-mock` provides
tools for making assertions about what `tracing` diagnostics are emitted
by code under test.

*Compiler support: [requires `rustc` 1.49+][msrv]*
*Compiler support: [requires `rustc` 1.56+][msrv]*

[msrv]: #supported-rust-versions

Expand Down Expand Up @@ -154,14 +154,14 @@ handle.assert_finished();
## Supported Rust Versions

Tracing is built against the latest stable release. The minimum supported
version is 1.49. The current Tracing version is not guaranteed to build on Rust
version is 1.56. The current Tracing version is not guaranteed to build on Rust
versions earlier than the minimum supported version.

Tracing follows the same compiler support policies as the rest of the Tokio
project. The current stable Rust compiler and the three most recent minor
versions before it will always be supported. For example, if the current stable
compiler version is 1.45, the minimum supported version will not be increased
past 1.42, three minor versions prior. Increasing the minimum supported compiler
compiler version is 1.69, the minimum supported version will not be increased
past 1.66, three minor versions prior. Increasing the minimum supported compiler
version is not considered a semver breaking change as long as doing so complies
with this policy.

Expand Down

0 comments on commit 887efb9

Please sign in to comment.