version bump

templates/manpage_template

@@ -32,7 +32,7 @@ Options:
 .TP
 .B
 \fB-a\fP
-about \fBjc\fP (JSON output)
+about \fBjc\fP (JSON or YAML output)
 .TP
 .B
 \fB-C\fP
@@ -69,6 +69,10 @@ unbuffer output (useful for slow streaming data with streaming parsers)
 .B
 \fB-v\fP
 version information
+.TP
+.B
+\fB-y\fP
+YAML output
 
 .SH EXIT CODES
 Any fatal errors within \fBjc\fP will generate an exit code of \fB100\fP, otherwise the exit code will be \fB0\fP. When using the "Magic" syntax (e.g. \fBjc ifconfig eth0\fP), \fBjc\fP will store the exit code of the program being parsed and add it to the \fBjc\fP exit code. This way it is easier to determine if an error was from the parsed program or \fBjc\fP.

templates/readme_template

@@ -149,8 +149,8 @@ option.
 | `{{ "{:>15}".format(parser.argument) }}` | {{ "{:<55}".format(parser.description) }} | {{ "{:<70}".format("[📃](https://kellyjonbrazil.github.io/jc/docs/parsers/" + parser.name + ")") }} |{% endfor %}
 
 ### Options
-- `-a` about `jc`. Prints information about `jc` and the parsers (in JSON, of
-       course!)
+- `-a` about `jc`. Prints information about `jc` and the parsers (in JSON or
+       YAML, of course!)
 - `-C` force color output even when using pipes (overrides `-m` and the
        `NO_COLOR` env variable)
 - `-d` debug mode. Prints trace messages if parsing issues are encountered (use
@@ -164,6 +164,7 @@ option.
        values and no additional semantic processing
 - `-u` unbuffer output
 - `-v` version information
+- `-y` YAML output
 
 ### Exit Codes
 Any fatal errors within `jc` will generate an exit code of `100`, otherwise the