mirror of
https://github.com/rust-lang/rust.git
synced 2025-02-24 04:46:58 +00:00
this is beta 1.49.0
This commit is contained in:
parent
a38f8fb674
commit
1bac1b40c8
@ -63,7 +63,7 @@ fi
|
||||
#
|
||||
# FIXME: need a scheme for changing this `nightly` value to `beta` and `stable`
|
||||
# either automatically or manually.
|
||||
export RUST_RELEASE_CHANNEL=nightly
|
||||
export RUST_RELEASE_CHANNEL=beta
|
||||
|
||||
# Always set the release channel for bootstrap; this is normally not important (i.e., only dist
|
||||
# builds would seem to matter) but in practice bootstrap wants to know whether we're targeting
|
||||
|
@ -12,15 +12,15 @@
|
||||
# source tarball for a stable release you'll likely see `1.x.0` for rustc and
|
||||
# `0.(x+1).0` for Cargo where they were released on `date`.
|
||||
|
||||
date: 2020-10-16
|
||||
rustc: beta
|
||||
cargo: beta
|
||||
date: 2020-11-16
|
||||
rustc: 1.48.0
|
||||
cargo: 1.48.0
|
||||
|
||||
# We use a nightly rustfmt to format the source because it solves some
|
||||
# bootstrapping issues with use of new syntax in this repo. If you're looking at
|
||||
# the beta/stable branch, this key should be omitted, as we don't want to depend
|
||||
# on rustfmt from nightly there.
|
||||
rustfmt: nightly-2020-10-12
|
||||
#rustfmt: nightly-2020-10-12
|
||||
|
||||
# When making a stable release the process currently looks like:
|
||||
#
|
||||
@ -40,4 +40,4 @@ rustfmt: nightly-2020-10-12
|
||||
# looking at a beta source tarball and it's uncommented we'll shortly comment it
|
||||
# out.
|
||||
|
||||
#dev: 1
|
||||
dev: 1
|
||||
|
Loading…
Reference in New Issue
Block a user