rustc/vendor/semver-1.0.24
2025-02-17 11:14:05 +01:00
..
benches New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
src New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
tests New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
.cargo-checksum.json New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
build.rs New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
Cargo.lock New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
Cargo.toml New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
LICENSE-APACHE New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
LICENSE-MIT New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00
README.md New upstream version 1.85.0~beta.9+dfsg1 2025-02-17 11:14:05 +01:00

semver

github crates.io docs.rs build status

A parser and evaluator for Cargo's flavor of Semantic Versioning.

Semantic Versioning (see https://semver.org) is a guideline for how version numbers are assigned and incremented. It is widely followed within the Cargo/crates.io ecosystem for Rust.

[dependencies]
semver = "1.0"

Compiler support: requires rustc 1.31+


Example

use semver::{BuildMetadata, Prerelease, Version, VersionReq};

fn main() {
    let req = VersionReq::parse(">=1.2.3, <1.8.0").unwrap();

    // Check whether this requirement matches version 1.2.3-alpha.1 (no)
    let version = Version {
        major: 1,
        minor: 2,
        patch: 3,
        pre: Prerelease::new("alpha.1").unwrap(),
        build: BuildMetadata::EMPTY,
    };
    assert!(!req.matches(&version));

    // Check whether it matches 1.3.0 (yes it does)
    let version = Version::parse("1.3.0").unwrap();
    assert!(req.matches(&version));
}

Scope of this crate

Besides Cargo, several other package ecosystems and package managers for other languages also use SemVer:RubyGems/Bundler for Ruby, npm for JavaScript, Composer for PHP, CocoaPods for Objective-C...

The semver crate is specifically intended to implement Cargo's interpretation of Semantic Versioning.

Where the various tools differ in their interpretation or implementation of the spec, this crate follows the implementation choices made by Cargo. If you are operating on version numbers from some other package ecosystem, you will want to use a different semver library which is appropriate to that ecosystem.

The extent of Cargo's SemVer support is documented in the Specifying Dependencies chapter of the Cargo reference.


License

Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.