rust
/
cargo
mirror of https://github.com/rust-lang/cargo
0
0
Fork 0
Code Issues Releases Wiki Activity
15,176 Commits 76 Branches 97 Tags 84 MiB
Rust 95.1%
Roff 4.4%
JavaScript 0.2%
Shell 0.2%
Go to file
bors 130825286f Auto merge of #13015 - ehuss:bump-stable-0.75.1, r=weihanglo 
[stable 1.74] Bump cargo patch version

https://github.com/rust-lang/cargo/pull/13004 bumped the credential crate versions to deal with a semver-incompatible change, but I believe we also need to bump and publish cargo.

My thinking is that:
* cargo 0.75.0 currently depends on cargo-credential-libsecret="0.3.1"
    * The `Cargo.lock` is locked to **0.3.2**
* We plan to yank cargo-credential-libsecret 0.3.2
* Users who depend on cargo 0.75.0 as a library will be unable to do so since after yanking it will pick up cargo-credential-libsecret="0.3.1", but this won't work.
    * cargo 0.75.0 -> cargo-credential 0.4.0
    * cargo-credential-libsecret 0.3.1 -> cargo-credential **0.3.0**

(Users using a `Cargo.lock`, like doing rust builds, shouldn't be affected by the yank.)

So, after publishing the new credential crates, I think we'll also need to publish a new 0.75.1 which depends on the correct versions so that users can use 0.75. It also probably makes sense to yank 0.75.0.
 		2023-11-20 03:04:43 +00:00
.cargo chore: remove `xtask-unpublished` 2023-08-01 22:54:41 +01:00
.github chore: bump to `cargo-semver-checks` 0.24.0 to support rustdoc json v27 2023-11-19 10:51:59 -05:00
benches feat(resolver): Respect MSRV 2023-08-25 10:42:26 -05:00
ci ci: integrate `xtask-bump-check` 2023-08-01 22:54:40 +01:00
crates refactor(test): Switch termcolor to anstream 2023-09-29 10:16:15 -05:00
credential chore: bump `cargo-credential-*` crates as e58b84d broke stuff 2023-11-19 09:57:17 -05:00
src Fix unused_imports warning 2023-11-19 10:17:24 -05:00
tests tests: Remove plugin tests 2023-11-19 10:48:16 -05:00
.gitignore chore(xtask): Add xtask skeleton 2023-04-25 02:13:56 -05:00
.ignore chore: Don't show genned docs in ripgrep 2022-08-31 16:13:32 -05:00
CHANGELOG.md chore: Fix typos 2023-09-19 15:28:48 -05:00
CODE_OF_CONDUCT.md Add CoC 2023-01-25 10:18:15 +00:00
CONTRIBUTING.md Add a notice about review capacity. 2022-03-24 14:18:42 -07:00
Cargo.lock [stable 1.74] Bump cargo patch version 2023-11-19 18:40:21 -08:00
Cargo.toml [stable 1.74] Bump cargo patch version 2023-11-19 18:40:21 -08:00
LICENSE-APACHE HTTPS all the things 2019-01-30 15:34:37 -05:00
LICENSE-MIT Remove inaccurate (misattributed) copyright notices 2017-07-26 17:19:24 -07:00
LICENSE-THIRD-PARTY HTTPS all the things 2019-01-30 15:34:37 -05:00
README.md doc: point to nightly cargo doc 2023-06-07 10:13:05 +01:00
build.rs clippy: allow usages of `std::env::var` family by exceptions 2023-03-17 12:57:21 +00:00
clippy.toml lint: follow convention no capitcal letter in first word 2023-09-14 13:43:47 +08:00
deny.toml Fix some typos 2023-09-24 23:10:07 +08:00
publish.py publish.py: Remove obsolete `sleep()` calls 2023-09-18 17:40:42 +02:00
triagebot.toml infra: add auto-trigger rules for new labels 2023-09-20 13:28:42 +08:00

README.md

Cargo

Cargo downloads your Rust project’s dependencies and compiles your project.

To start using Cargo, learn more at The Cargo Book.

To start developing Cargo itself, read the Cargo Contributor Guide.

Code Status

CI

Code documentation: https://doc.rust-lang.org/nightly/nightly-rustc/cargo/

Installing Cargo

Cargo is distributed by default with Rust, so if you've got rustc installed locally you probably also have cargo installed locally.

Compiling from Source

Requirements

Cargo requires the following tools and packages to build:

Other requirements:

The following are optional based on your platform and needs.

  • pkg-config — This is used to help locate system packages, such as libssl headers/libraries. This may not be required in all cases, such as using vendored OpenSSL, or on Windows.

  • OpenSSL — Only needed on Unix-like systems and only if the vendored-openssl Cargo feature is not used.

    This requires the development headers, which can be obtained from the libssl-dev package on Ubuntu or openssl-devel with apk or yum or the openssl package from Homebrew on macOS.

    If using the vendored-openssl Cargo feature, then a static copy of OpenSSL will be built from source instead of using the system OpenSSL. This may require additional tools such as perl and make.

    On macOS, common installation directories from Homebrew, MacPorts, or pkgsrc will be checked. Otherwise it will fall back to pkg-config.

    On Windows, the system-provided Schannel will be used instead.

    LibreSSL is also supported.

Optional system libraries:

The build will automatically use vendored versions of the following libraries. However, if they are provided by the system and can be found with pkg-config, then the system libraries will be used instead:

  • libcurl — Used for network transfers.
  • libgit2 — Used for fetching git dependencies.
  • libssh2 — Used for SSH access to git repositories.
  • libz (aka zlib) — Used for data compression.

It is recommended to use the vendored versions as they are the versions that are tested to work with Cargo.

Compiling

First, you'll want to check out this repository

git clone https://github.com/rust-lang/cargo.git
cd cargo

With cargo already installed, you can simply run:

cargo build --release

Adding new subcommands to Cargo

Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See the Wiki page for more details and a list of known community-developed subcommands.

Releases

Cargo releases coincide with Rust releases. High level release notes are available as part of Rust's release notes. Detailed release notes are available in this repo at CHANGELOG.md.

Reporting issues

Found a bug? We'd love to know about it!

Please report all issues on the GitHub issue tracker.

Contributing

See the Cargo Contributor Guide for a complete introduction to contributing to Cargo.

License

Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

Third party software

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (https://www.openssl.org/).

In binary form, this product includes software that is licensed under the terms of the GNU General Public License, version 2, with a linking exception, which can be obtained from the upstream repository.

See LICENSE-THIRD-PARTY for details.