ci: release 0.2.0

Author: chevdor

Cargo.lock

@@ -2,7 +2,7 @@
 authors = ["chevdor <chevdor@gmail.com>"]
 edition = "2018"
 name = "tera-cli"
-version = "0.1.3"
+version = "0.2.0"
 description = "A command line utility written in Rust to render templates from json|toml|yaml && ENV, using the tera templating engine"
 readme = "README.md"
 license = "MIT"
@@ -18,7 +18,7 @@ tera = "1.12"
 toml = {version = "0.5", optional = false}
 
 [dev-dependencies]
-assert_cmd = "1.0"
+assert_cmd = "2.0"
 predicates = "2.0"
 
 [[bin]]

Cargo.toml

@@ -34,7 +34,6 @@ RUN set -eux \
     && echo ">>> FINISHED COMPILING 'tera-cli'"
 
 # ------------------------------------------------------------------------------
-# ------------------------------------------------------------------------------
 
 FROM alpine
 

Dockerfile

@@ -160,16 +160,18 @@ Passing the `-a | --escape` flag allows escaping the content.
 
 ## Usage
 
-    tera-cli 0.1.3
+    tera-cli 0.2.0
+
     chevdor <chevdor@gmail.com>
+
     Command line utility for the tera templating engine. You need to provide a template using the tera
     syntax as well as some data (various format are supported)
 
     USAGE:
-        tera [FLAGS] [OPTIONS] --template <template> [context]
+        tera [FLAGS] [OPTIONS] --template <TEMPLATE> [CONTEXT]
 
     ARGS:
-        <context>    Location of the context data. This file can be of the following type: json |
+        <CONTEXT>    Location of the context data. This file can be of the following type: json |
                      toml | yaml. If you prefer to pass the data as stdin, use `--stdin`
 
     FLAGS:
@@ -183,21 +185,24 @@ Passing the `-a | --escape` flag allows escaping the content.
                                    option. This will prevent an error about no context being passed to
                                    be raised
             --fail-on-collision    if you prefer your data to override the ENV
-        -h, --help                 Prints help information
+        -h, --help                 Print help information
         -i, --include              This flag tells the command to parse all templates found in the same
                                    path where the given template is located [aliases: inherit]
         -s, --stdin                The context data can be passed using stdin
-        -V, --version              Prints version information
+        -V, --version              Print version information
 
     OPTIONS:
-            --env-key <env-key>
+            --env-key <ENV_KEY>
                 By default, if --env is set, the environment variables will be attached at the root of
                 the context. This is convenient but may end up conflicting with your data. To prevent
                 collisions, you can provide a custom key with this option
 
-            --include-path <include-path>
+            --include-path <INCLUDE_PATH>
                 Option to define a different path from which search and parse templates [aliases:
                 inherit-path]
 
-        -o, --out <out>                      Optional output file. If not passed, using stdout
-        -t, --template <template>            Location of the template
+        -o, --out <OUT>
+                Optional output file. If not passed, using stdout
+
+        -t, --template <TEMPLATE>
+                Location of the template

README.md

@@ -1,13 +1,15 @@
-tera-cli 0.1.3
+tera-cli 0.2.0
+
 chevdor <chevdor@gmail.com>
+
 Command line utility for the tera templating engine. You need to provide a template using the tera
 syntax as well as some data (various format are supported)
 
 USAGE:
-    tera [FLAGS] [OPTIONS] --template <template> [context]
+    tera [FLAGS] [OPTIONS] --template <TEMPLATE> [CONTEXT]
 
 ARGS:
-    <context>    Location of the context data. This file can be of the following type: json |
+    <CONTEXT>    Location of the context data. This file can be of the following type: json |
                  toml | yaml. If you prefer to pass the data as stdin, use `--stdin`
 
 FLAGS:
@@ -21,21 +23,24 @@ FLAGS:
                                option. This will prevent an error about no context being passed to
                                be raised
         --fail-on-collision    if you prefer your data to override the ENV
-    -h, --help                 Prints help information
+    -h, --help                 Print help information
     -i, --include              This flag tells the command to parse all templates found in the same
                                path where the given template is located [aliases: inherit]
     -s, --stdin                The context data can be passed using stdin
-    -V, --version              Prints version information
+    -V, --version              Print version information
 
 OPTIONS:
-        --env-key <env-key>
+        --env-key <ENV_KEY>
             By default, if --env is set, the environment variables will be attached at the root of
             the context. This is convenient but may end up conflicting with your data. To prevent
             collisions, you can provide a custom key with this option
 
-        --include-path <include-path>
+        --include-path <INCLUDE_PATH>
             Option to define a different path from which search and parse templates [aliases:
             inherit-path]
 
-    -o, --out <out>                      Optional output file. If not passed, using stdout
-    -t, --template <template>            Location of the template
+    -o, --out <OUT>
+            Optional output file. If not passed, using stdout
+
+    -t, --template <TEMPLATE>
+            Location of the template

doc/usage.adoc

@@ -42,3 +42,6 @@ brew:
 	SITE=https://github.com
 	REPO=chevdor/tera-cli
 	tera --template templates/formula.rb --env-only > Formula/tera.rb
+
+bump:
+	cargo workspaces version --no-git-push