Skip to content

Commit

Permalink
document MSRV, remove 1.31.1 from travis
Browse files Browse the repository at this point in the history
  • Loading branch information
warner committed Aug 7, 2019
1 parent 414b4dc commit f6cbefd
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 2 deletions.
2 changes: 0 additions & 2 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,6 @@ rust:
- stable
- beta
- nightly
- 1.31.1
- 1.32.0
matrix:
include:
Expand All @@ -16,5 +15,4 @@ matrix:
allow_failures:
- rust: nightly
- env: RUSTFMT
- rust: 1.31.1
script: cargo test --release --verbose --all
17 changes: 17 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,23 @@ the memory.
| [SRP][2] | [![crates.io](https://img.shields.io/crates/v/srp.svg)](https://crates.io/crates/srp) | [![Documentation](https://docs.rs/srp/badge.svg)](https://docs.rs/srp) |
| [spake2][4] | [![crates.io](https://img.shields.io/crates/v/spake2.svg)](https://crates.io/crates/spake2) | [![Documentation](https://docs.rs/spake2/badge.svg)](https://docs.rs/spake2) |

## Rust version requirements

The MSRV (Minimum Supported Rust Version) is 1.32.0 . If/when this changes,
it will be noted in the changelog, and the crate semver will be updated. So
downstream projects should depend upon e.g. `spake2 = "0.2"` to avoid picking
up new versions that would require a newer compiler.

SRP-v0.4.1 actually works with rustc-1.31.1, but this will probably be
changed in the next release.

SPAKE2 required rustc-1.32 beginning with spake2-v0.2.0 .

Our CI scripts check all builds against a pinned version of rustc to test the
intended MSRV. Sometimes upstream dependencies make surprising changes that
could require a newer version of rustc, without changes to the source code in
this repository, but hopefully this won't happen very frequently.

## License

All crates are licensed under either of
Expand Down

0 comments on commit f6cbefd

Please sign in to comment.