release

sagiegurari · Jul 31, 2020 · 2effff0 · 2effff0
1 parent 0bf26bd
commit 2effff0
Show file tree

Hide file tree

Showing 38 changed files with 212 additions and 230 deletions.
diff --git a/.buildnumber b/.buildnumber
@@ -1 +1 @@
-200
+201
diff --git a/Cargo.toml b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "cargo-make"
-version = "0.32.0"
+version = "0.32.1"
 authors = ["Sagie Gur-Ari <sagiegurari@gmail.com>"]
 description = "Rust task runner and build tool."
 license = "Apache-2.0"

diff --git a/README.md b/README.md
@@ -200,7 +200,7 @@ cargo make --makefile simple-example.toml my-flow
 The output would look something like this:
 
 ```console
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: simple-example.toml
 [cargo-make] INFO - Task: my-flow
 [cargo-make] INFO - Setting Up Env.
@@ -572,7 +572,7 @@ Invoking cargo-make with additional arguments would result in the following:
 ```console
 > cargo make varargs arg1 arg2 arg3
 
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: Makefile.toml
 [cargo-make] INFO - Task: varargs
 [cargo-make] INFO - Setting Up Env.
@@ -589,7 +589,7 @@ Invoking cargo-make without any additional arguments would result in the followi
 ```console
 > cargo make varargs
 
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: Makefile.toml
 [cargo-make] INFO - Task: varargs
 [cargo-make] INFO - Setting Up Env.
@@ -616,7 +616,7 @@ Would output:
 ```console
 > cargo make varargs arg1 arg2 arg3
 
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: Makefile.toml
 [cargo-make] INFO - Task: varargs
 [cargo-make] INFO - Setting Up Env.
@@ -671,7 +671,7 @@ Invoking cargo-make with additional arguments would result in the following:
 ```console
 > cargo make cli-args arg1 arg2 arg3
 
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: Makefile.toml
 [cargo-make] INFO - Task: cli-args
 [cargo-make] INFO - Setting Up Env.
@@ -688,7 +688,7 @@ Invoking cargo-make without any additional arguments would result in the followi
 ```console
 > cargo make cli-args
 
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: Makefile.toml
 [cargo-make] INFO - Task: cli-args
 [cargo-make] INFO - Setting Up Env.
@@ -917,7 +917,7 @@ Output:
 
 ```console
 > cargo make --cwd ./examples --makefile ./shebang.toml shebang-sh
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: ./shebang.toml
 [cargo-make] INFO - Task: shebang-sh
 [cargo-make] INFO - Profile: development
@@ -946,7 +946,7 @@ Output:
 
 ```console
 > cargo make --cwd ./examples --makefile ./shebang.toml shebang-python
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: ./shebang.toml
 [cargo-make] INFO - Task: shebang-python
 [cargo-make] INFO - Profile: development
@@ -1234,7 +1234,7 @@ args = ["3"]
 We run task **3** the output would be:
 
 ```console
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: task_extend.toml
 [cargo-make] INFO - Task: 3
 [cargo-make] INFO - Profile: development
@@ -1263,7 +1263,7 @@ You can define env vars to be set as part of the execution of the flow in the gl
 
 ```toml
 [env]
-RUST_BACKTRACE = "1"
+RUST_BACKTRACE = 1
 EVALUATED_VAR = { script = ["echo SOME VALUE"] }
 TEST1 = "value1"
 TEST2 = "value2"
@@ -1288,9 +1288,9 @@ PROD = true
 
 Environment variables can be defined as:
 
-* Simple key/value pair, where the value can be either string or boolean
+* Simple key/value pair, where the value can be either string, boolean or a number.
 ```toml
-RUST_BACKTRACE = "1"
+RUST_BACKTRACE = 1
 BOOL_VALUE = true
 ```
 * Key and an array which will be joined with the ';' separator
@@ -2180,7 +2180,7 @@ cargo make --cwd ./examples --makefile profile.toml --profile production echo
 Output:
 
 ```console
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: profile.toml
 [cargo-make] INFO - Task: echo
 [cargo-make] INFO - Profile: production
@@ -2299,7 +2299,7 @@ deprecated = true
 When invoking **legacy** task for example, the output is:
 
 ```console
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: deprecated.toml
 [cargo-make] INFO - Task: legacy
 [cargo-make] INFO - Profile: development
@@ -2340,15 +2340,15 @@ watch = true
 Below is a sample output of invoking the task:
 
 ```console
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: ./examples/watch.toml
 [cargo-make] INFO - Task: watch-example
 [cargo-make] INFO - Setting Up Env.
 [cargo-make] INFO - Running Task: init
 [cargo-make] INFO - Running Task: watch-example
 [cargo-make] INFO - Running Task: watch-example-watch
 [cargo-make] INFO - Execute Command: "cargo" "watch" "-q" "-x" "make --disable-check-for-updates --no-on-error --loglevel=info --makefile=/projects/rust/cargo-make/examples/watch.toml watch-example"
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: /projects/rust/cargo-make/examples/watch.toml
 [cargo-make] INFO - Task: watch-example
 [cargo-make] INFO - Setting Up Env.
@@ -2418,7 +2418,7 @@ args = ["${MULTIPLE_VALUES}"]
 
 ```console
 > cargo make --cwd ./examples --makefile functions.toml split
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: split
 [cargo-make] INFO - Profile: development
@@ -2430,7 +2430,7 @@ args = ["${MULTIPLE_VALUES}"]
 [cargo-make] INFO - Build Done  in 0 seconds.
 
 > cargo make --cwd ./examples --makefile functions.toml no-split
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: no-split
 [cargo-make] INFO - Profile: development
@@ -2465,7 +2465,7 @@ args = ["@@getat(MULTIPLE_VALUES,|,3)"]
 
 ```console
 > cargo make --cwd ./examples --makefile functions.toml getat
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: getat
 [cargo-make] INFO - Profile: development
@@ -2492,7 +2492,7 @@ args = ["1", "@@remove-empty(DOES_NOT_EXIST)", "2"]
 
 ```console
 > cargo make --cwd ./examples --makefile functions.toml remove-empty
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: remove-empty
 [cargo-make] INFO - Profile: development
@@ -2525,7 +2525,7 @@ args = ["@@trim(TRIM_VALUE)"]
 
 ```console
 > cargo make --cwd ./examples --makefile functions.toml remove-empty
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: trim
 [cargo-make] INFO - Profile: development
@@ -2554,7 +2554,7 @@ args = ["@@trim(TRIM_VALUE,end)"]
 
 ```console
 > cargo make --cwd ./examples --makefile functions.toml trim-start
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: trim-start
 [cargo-make] INFO - Profile: development
@@ -2566,7 +2566,7 @@ args = ["@@trim(TRIM_VALUE,end)"]
 [cargo-make] INFO - Build Done  in 0 seconds.
 
 > cargo make --cwd ./examples --makefile functions.toml trim-end
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: trim-end
 [cargo-make] INFO - Profile: development
@@ -2604,7 +2604,7 @@ Sample run for a mapping that was found:
 
 ```console
 cargo make --cwd ./examples --makefile functions.toml -e DECODE_ENV_VAR=development decode
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: decode
 [cargo-make] INFO - Profile: development
@@ -2620,7 +2620,7 @@ Another sample run for a mapping that was not found:
 
 ```console
 cargo make --cwd ./examples --makefile functions.toml -e DECODE_ENV_VAR=unmapped decode
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: decode
 [cargo-make] INFO - Profile: development
@@ -2645,7 +2645,7 @@ Sample run:
 
 ```console
 cargo make --cwd ./examples --makefile functions.toml -e DECODE_ENV_VAR=unmapped decode-with-default
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: decode-with-default
 [cargo-make] INFO - Profile: development
@@ -2669,7 +2669,7 @@ Sample run:
 
 ```console
 cargo make --cwd ./examples --makefile functions.toml -e DECODE_ENV_VAR=test decode-with-eval
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: functions.toml
 [cargo-make] INFO - Task: decode-with-eval
 [cargo-make] INFO - Profile: development
@@ -3024,7 +3024,7 @@ In order to specify the minimal version, use the **min_version** in the config s
 
 ```toml
 [config]
-min_version = "0.32.0"
+min_version = "0.32.1"
 ```
 
 <a name="usage-diff-changes"></a>
@@ -3035,7 +3035,7 @@ Example Usage:
 
 ```console
 cargo make --diff-steps --makefile ./examples/override_core.toml post-build
-[cargo-make] INFO - cargo make 0.32.0
+[cargo-make] INFO - cargo make 0.32.1
 [cargo-make] INFO - Build File: ./examples/override_core.toml
 [cargo-make] INFO - Task: post-build
 [cargo-make] INFO - Setting Up Env.

diff --git a/docs/_config.yml b/docs/_config.yml
@@ -2,4 +2,4 @@ theme: jekyll-theme-cayman
 title: cargo-make
 description: Rust task runner and build tool.
 show_downloads: false
-version: 0.32.0
+version: 0.32.1
diff --git a/docs/_includes/content.md b/docs/_includes/content.md
@@ -1152,7 +1152,7 @@ You can define env vars to be set as part of the execution of the flow in the gl
 
 ```toml
 [env]
-RUST_BACKTRACE = "1"
+RUST_BACKTRACE = 1
 EVALUATED_VAR = { script = ["echo SOME VALUE"] }
 TEST1 = "value1"
 TEST2 = "value2"
@@ -1177,9 +1177,9 @@ PROD = true
 
 Environment variables can be defined as:
 
-* Simple key/value pair, where the value can be either string or boolean
+* Simple key/value pair, where the value can be either string, boolean or a number.
 ```toml
-RUST_BACKTRACE = "1"
+RUST_BACKTRACE = 1
 BOOL_VALUE = true
 ```
 * Key and an array which will be joined with the ';' separator