Closed renovate[bot] closed 9 months ago
Why? Bumping the MSRV is a breaking change and shouldn't be done if the project doesn't actually need it, and if it does it should be marked as breaking. Just bumping because you can is a terrible idea.
Bumping MSRV is not generally recognized as a breaking change. It is subset of "build environment requirements". If those were considered breaking changes, then every time rustc demotes a target between tiers, requires new glibc, etc, rustc would need to bump its major version.
As for proactively bumping MSRV,
Rarely have I seen someone have a fixed MSRV policy that can generally work for people (Debian being one of the main ones). Instead other open source projects tend to have a sliding MSRV window, like 3 releases or 6 months, so making my MSRV policy variable does not help any of them.
This PR contains the following updates:
1.69.0
->1.73
1.76
(+2)1.69
->1.73
1.76
(+2)Release Notes
rust-lang/rust (rust)
### [`v1.73`](https://togithub.com/rust-lang/rust/blob/HEAD/RELEASES.md#Version-1730-2023-10-05) [Compare Source](https://togithub.com/rust-lang/rust/compare/1.72.0...1.73.0) \========================== ## Language - [Uplift `clippy::fn_null_check` lint as `useless_ptr_null_checks`.](https://togithub.com/rust-lang/rust/pull/111717/) - [Make `noop_method_call` warn by default.](https://togithub.com/rust-lang/rust/pull/111916/) - [Support interpolated block for `try` and `async` in macros.](https://togithub.com/rust-lang/rust/pull/112953/) - [Make `unconditional_recursion` lint detect recursive drops.](https://togithub.com/rust-lang/rust/pull/113902/) - [Future compatibility warning for some impls being incorrectly considered not overlapping.](https://togithub.com/rust-lang/rust/pull/114023/) - [The `invalid_reference_casting` lint is now **deny-by-default** (instead of allow-by-default)](https://togithub.com/rust-lang/rust/pull/112431) ## Compiler - [Write version information in a `.comment` section like GCC/Clang.](https://togithub.com/rust-lang/rust/pull/97550/) - [Add documentation on v0 symbol mangling.](https://togithub.com/rust-lang/rust/pull/97571/) - [Stabilize `extern "thiscall"` and `"thiscall-unwind"` ABIs.](https://togithub.com/rust-lang/rust/pull/114562/) - [Only check outlives goals on impl compared to trait.](https://togithub.com/rust-lang/rust/pull/109356/) - [Infer type in irrefutable slice patterns with fixed length as array.](https://togithub.com/rust-lang/rust/pull/113199/) - [Discard default auto trait impls if explicit ones exist.](https://togithub.com/rust-lang/rust/pull/113312/) - Add several new tier 3 targets: - [`aarch64-unknown-teeos`](https://togithub.com/rust-lang/rust/pull/113480/) - [`csky-unknown-linux-gnuabiv2`](https://togithub.com/rust-lang/rust/pull/113658/) - [`riscv64-linux-android`](https://togithub.com/rust-lang/rust/pull/112858/) - [`riscv64gc-unknown-hermit`](https://togithub.com/rust-lang/rust/pull/114004/) - [`x86_64-unikraft-linux-musl`](https://togithub.com/rust-lang/rust/pull/113411/) - [`x86_64-unknown-linux-ohos`](https://togithub.com/rust-lang/rust/pull/113061/) - [Add `wasm32-wasi-preview1-threads` as a tier 2 target.](https://togithub.com/rust-lang/rust/pull/112922/) Refer to Rust's \[platform support page]\[platform-support-doc] for more information on Rust's tiered platform support. ## Libraries - [Add `Read`, `Write` and `Seek` impls for `ArcConfiguration
📅 Schedule: Branch creation - " *" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.