Feature Overview
We currently specify the MSRV in the [workspace.package] section of ./Cargo.toml:
|
[workspace.package] |
|
version = "21.1.1" |
|
license = "Apache-2.0" |
|
edition = "2024" |
|
rust-version = "1.89" |
|
repository = "https://github.com/OpenDevicePartnership/patina" |
However, we do not currently have automated testing against that version.
Solution Overview
This issue tracks:
- Verifying the MSRV build on changes to
rust-toolchain.toml (PR gates)
- Verifying the MSRV build nightly
It has been rare so far that a change is made that unintentionally breaks the MSRV build so this is a tradeoff to getting test data back without too much overhead.
If a MSRV failure is found, a GitHub issue should automatically be created that identifies the versions involved and tracks a fix. It should automatically be closed when the "MSRV Check" workflow succeeds.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
I will implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
Feature Overview
We currently specify the MSRV in the
[workspace.package]section of./Cargo.toml:patina/Cargo.toml
Lines 5 to 10 in e9d665e
However, we do not currently have automated testing against that version.
Solution Overview
This issue tracks:
rust-toolchain.toml(PR gates)It has been rare so far that a change is made that unintentionally breaks the MSRV build so this is a tradeoff to getting test data back without too much overhead.
If a MSRV failure is found, a GitHub issue should automatically be created that identifies the versions involved and tracks a fix. It should automatically be closed when the "MSRV Check" workflow succeeds.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
I will implement the feature
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response