File tree Expand file tree Collapse file tree 2 files changed +7
-6
lines changed Expand file tree Collapse file tree 2 files changed +7
-6
lines changed Original file line number Diff line number Diff line change @@ -13,7 +13,7 @@ use build_helper::output;
1313use crate :: Build ;
1414
1515// The version number
16- pub const CFG_RELEASE_NUM : & str = "1.42 .0" ;
16+ pub const CFG_RELEASE_NUM : & str = "1.43 .0" ;
1717
1818pub struct GitInfo {
1919 inner : Option < Info > ,
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: 2019-12-18
15+ date: 2020-01-30
1616rustc: beta
1717cargo: beta
1818
19- # We use a nightly rustfmt to format the source because it solves some bootstrapping
20- # issues with use of new syntax in this repo. If you're looking at the beta/stable branch, this key should be omitted,
21- # as we don't want to depend on rustfmt from nightly there.
22- rustfmt: nightly-2019-12-18
19+ # We use a nightly rustfmt to format the source because it solves some
20+ # bootstrapping issues with use of new syntax in this repo. If you're looking at
21+ # the beta/stable branch, this key should be omitted, as we don't want to depend
22+ # on rustfmt from nightly there.
23+ rustfmt: nightly-2020-01-31
2324
2425# When making a stable release the process currently looks like:
2526#
You can’t perform that action at this time.
0 commit comments