| commit | 22cbf44b0d906fa82658557eead43b8d1f9caac0 | [log] [tgz] |
|---|---|---|
| author | James Farrell <[email protected]> | Thu Aug 29 16:49:55 2024 +0000 |
| committer | James Farrell <[email protected]> | Thu Aug 29 16:49:55 2024 +0000 |
| tree | f6bc5adbb77666f7eba851b3188d736d1757bb04 | |
| parent | 42fe742c4a140c04a6158f7ea3b2d323c738c24c [diff] |
Migrate 25 crates to monorepo. sec1 semver serde_cbor serde_derive shared_library slab smallvec smccc socket2 spin spki strsim strum strum_macros sync_wrapper syn-mid synstructure tempfile termcolor termtree textwrap thiserror thread_local tinytemplate tokio-macros Bug: 339424309 Test: treehugger Change-Id: Ic44c007a78f4af197997faccb3065bfb30352414
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+
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)); }
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.