Merge pull request #1310 from TheBlueMatt/2022-02-bump-msrv

Bump MSRV to 1.41.1.
This commit is contained in:
Matt Corallo 2022-03-02 19:09:14 +00:00 committed by GitHub
commit 5e86bbf970
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 8 deletions

View file

@ -10,10 +10,8 @@ jobs:
platform: [ ubuntu-latest ] platform: [ ubuntu-latest ]
toolchain: [ stable, toolchain: [ stable,
beta, beta,
# 1.36.0 is MSRV for Rust-Lightning, lightning-invoice, and lightning-persister # 1.41.1 is MSRV for Rust-Lightning, lightning-invoice, and lightning-persister
1.36.0, 1.41.1,
# 1.41.0 is Debian stable
1.41.0,
# 1.45.2 is MSRV for lightning-net-tokio, lightning-block-sync, and coverage generation # 1.45.2 is MSRV for lightning-net-tokio, lightning-block-sync, and coverage generation
1.45.2, 1.45.2,
# 1.47.0 will be the MSRV for no-std builds using hashbrown once core2 is updated # 1.47.0 will be the MSRV for no-std builds using hashbrown once core2 is updated
@ -41,11 +39,9 @@ jobs:
- toolchain: beta - toolchain: beta
build-net-tokio: true build-net-tokio: true
build-no-std: true build-no-std: true
- toolchain: 1.36.0 - toolchain: 1.41.1
build-no-std: false build-no-std: false
test-log-variants: true test-log-variants: true
- toolchain: 1.41.0
build-no-std: false
- toolchain: 1.45.2 - toolchain: 1.45.2
build-net-old-tokio: true build-net-old-tokio: true
build-net-tokio: true build-net-tokio: true

View file

@ -75,7 +75,7 @@ be covered by functional tests.
When refactoring, structure your PR to make it easy to review and don't When refactoring, structure your PR to make it easy to review and don't
hestitate to split it into multiple small, focused PRs. hestitate to split it into multiple small, focused PRs.
The Minimal Supported Rust Version is 1.36.0 (enforced by our GitHub Actions). The Minimum Supported Rust Version is 1.41.1 (enforced by our GitHub Actions).
Commits should cover both the issue fixed and the solution's rationale. Commits should cover both the issue fixed and the solution's rationale.
These [guidelines](https://chris.beams.io/posts/git-commit/) should be kept in mind. These [guidelines](https://chris.beams.io/posts/git-commit/) should be kept in mind.