From 22f4fa7ea24c4faea562bcbb8b9e9ed515346ec0 Mon Sep 17 00:00:00 2001
From: Pietro Albini <pietro@pietroalbini.org>
Date: Tue, 5 Nov 2019 09:41:16 +0100
Subject: [PATCH] this is beta 1.40.0

---
 src/ci/run.sh  | 2 +-
 src/stage0.txt | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/src/ci/run.sh b/src/ci/run.sh
index bce35670c8d46..c2caf6c9f4333 100755
--- a/src/ci/run.sh
+++ b/src/ci/run.sh
@@ -45,7 +45,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
 if [ "$DEPLOY$DEPLOY_ALT" = "1" ]; then
   RUST_CONFIGURE_ARGS="$RUST_CONFIGURE_ARGS --release-channel=$RUST_RELEASE_CHANNEL"
   RUST_CONFIGURE_ARGS="$RUST_CONFIGURE_ARGS --enable-llvm-static-stdcpp"
diff --git a/src/stage0.txt b/src/stage0.txt
index 9509d3e99612f..66f7e377b796b 100644
--- a/src/stage0.txt
+++ b/src/stage0.txt
@@ -12,9 +12,9 @@
 # source tarball for a stable release you'll likely see `1.x.0` for rustc and
 # `0.x.0` for Cargo where they were released on `date`.
 
-date: 2019-09-25
-rustc: beta
-cargo: beta
+date: 2019-11-04
+rustc: 1.39.0
+cargo: 0.40.0
 
 # When making a stable release the process currently looks like:
 #
@@ -34,4 +34,4 @@ cargo: beta
 # looking at a beta source tarball and it's uncommented we'll shortly comment it
 # out.
 
-#dev: 1
+dev: 1