itsscb/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo.git synced 2025-10-01 11:30:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto merge of #14539 - ehuss:update-release-docs, r=weihanglo

Browse Source 
Update docs for how cargo is published

This updates the docs for publishing crates in this repo after the changes from https://github.com/rust-lang/cargo/pull/14202.
This commit is contained in:
bors 2024-09-11 21:08:31 +00:00
commit 9736f3204a
1 changed files with 17 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
src/doc/contrib/src/process/release.md
View File

@ -26,7 +26,7 @@ Every night at 00:00 UTC, the artifacts from the most recently merged PR are
promoted to the nightly release channel. A similar process happens for beta promoted to the nightly release channel. A similar process happens for beta
and stable releases. and stable releases.
[`dist` bootstrap module]: https://github.com/rust-lang/rust/blob/master/src/bootstrap/dist.rs [`dist` bootstrap module]: https://github.com/rust-lang/rust/blob/master/src/bootstrap/src/core/build_steps/dist.rs
## Submodule updates ## Submodule updates
@ -123,17 +123,21 @@ stable) and the release-specific URL such as
The code that builds the documentation is located in the [`doc` bootstrap The code that builds the documentation is located in the [`doc` bootstrap
module]. module].
[`doc` bootstrap module]: https://github.com/rust-lang/rust/blob/master/src/bootstrap/doc.rs [`doc` bootstrap module]: https://github.com/rust-lang/rust/blob/master/src/bootstrap/src/core/build_steps/doc.rs
## crates.io publishing ## crates.io publishing
Cargo's library and its related dependencies (like `cargo-util`) are published Cargo's library and its related dependencies (like `cargo-util`) are published
to [crates.io] as part of the 6-week stable release process by the [Release to [crates.io] as part of the 6-week stable release process by the [Release
team]. There is a [`publish.py` script] that is used by the Release team's team]. The release process involves a series of steps:
automation scripts (see <https://github.com/rust-lang/simpleinfra/>) to handle
determining which packages to publish. The build tool crates aren't published. 1. The Release team's automation scripts (see <https://github.com/rust-lang/simpleinfra/>) will run [`promote-release`] which will create a tag in the `rust-lang/cargo` repository associated with the version of the cargo submodule for that release.
This runs on the specific git commit associated with the cargo submodule in the 2. The creation of a tag will trigger the [release workflow] in `rust-lang/cargo`.
`stable` branch in `rust-lang/rust` at the time of release. 3. The release workflow will run the [`publish.py` script] on the commit associated with the tag.
4. The `publish.py` script will run `cargo publish` on any crates that are not already published.
[`promote-release`]: https://github.com/rust-lang/promote-release
[release workflow]: https://github.com/rust-lang/cargo/blob/master/.github/workflows/release.yml
On very rare cases, the Cargo team may decide to manually publish a new On very rare cases, the Cargo team may decide to manually publish a new
release to [crates.io]. For example, this may be necessary if there is a release to [crates.io]. For example, this may be necessary if there is a
@ -141,20 +145,17 @@ problem with the current version that only affects API users, and does not
affect the `cargo` binary shipped in the stable release. In this situation, affect the `cargo` binary shipped in the stable release. In this situation,
PRs should be merged to the associated stable release branch in the cargo repo PRs should be merged to the associated stable release branch in the cargo repo
(like `rust-1.70.0`) that fix the issue and bump the patch version of the (like `rust-1.70.0`) that fix the issue and bump the patch version of the
affected package. Then someone with permissions (currently a subset of the affected package. Then you need to work with the Release Team to get a release
Cargo team, or the Release team) should publish it manually using `cargo published to crates.io.[^release-problem]
publish`.
Some packages are not published automatically because they are not part of the Some packages are not published automatically because they are not part of the
Rust release train. This currently only includes the [`home`] package. These Rust release train. This currently only includes the [`home`] package. These
are published manually on an as-needed or as-requested basis by whoever has are published manually on an as-needed or as-requested basis by whoever has
permissions (currently [@ehuss] or the Release/Infra team). permissions (currently [@ehuss] or the Release/Infra team)[^fix-manual-release].
In the future, these manual publishing options should be integrated with [^release-problem]: Unfortunately there are some complications with this process. See <https://github.com/rust-lang/cargo/issues/14538> for more detail, and thoughts on how to improve this.
GitHub Actions so that any team member can trigger them. Likely that should
involve getting Infra to create scoped tokens that can be added as GitHub [^fix-manual-release]: This should be fixed, see [crate ownership policy](https://forge.rust-lang.org/policies/crate-ownership.html) about removing ownership. Also see <https://github.com/rust-lang/cargo/issues/14538> for problems with tagging. In general, these should be published from GitHub Actions, but we don't have the infrastructure set up for that, yet.
Secrets, and setting up GitHub Actions workflows with the appropriate
permissions which can be manually triggered to launch a release.
[`home`]: https://github.com/rust-lang/cargo/tree/master/crates/home [`home`]: https://github.com/rust-lang/cargo/tree/master/crates/home
[`publish.py` script]: https://github.com/rust-lang/cargo/blob/master/publish.py [`publish.py` script]: https://github.com/rust-lang/cargo/blob/master/publish.py