File tree Expand file tree Collapse file tree 3 files changed +4
-5
lines changed Expand file tree Collapse file tree 3 files changed +4
-5
lines changed Original file line number Diff line number Diff line change @@ -31,7 +31,6 @@ python2.7 "$X_PY" test --no-fail-fast \
3131 src/doc/rust-by-example \
3232 src/tools/rls \
3333 src/tools/rustfmt \
34- src/tools/miri \
3534 src/tools/clippy
3635set -e
3736
Original file line number Diff line number Diff line change 4444#
4545# FIXME: need a scheme for changing this `nightly` value to `beta` and `stable`
4646# either automatically or manually.
47- export RUST_RELEASE_CHANNEL=nightly
47+ export RUST_RELEASE_CHANNEL=beta
4848if [ " $DEPLOY$DEPLOY_ALT " != " " ]; then
4949 RUST_CONFIGURE_ARGS=" $RUST_CONFIGURE_ARGS --release-channel=$RUST_RELEASE_CHANNEL "
5050 RUST_CONFIGURE_ARGS=" $RUST_CONFIGURE_ARGS --enable-llvm-static-stdcpp"
Original file line number Diff line number Diff line change 1212# source tarball for a stable release you'll likely see `1.x.0` for rustc and
1313# `0.x.0` for Cargo where they were released on `date`.
1414
15- date: 2018-03-18
16- rustc: beta
17- cargo: beta
15+ date: 2018-03-29
16+ rustc: 1.25.0
17+ cargo: 0.26.0
1818
1919# When making a stable release the process currently looks like:
2020#
You can’t perform that action at this time.
0 commit comments