version 0.16.0 - pattern compositionv0.16.0

4 files changed, 10 insertions, 6 deletions

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1977fdf..bd0053b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,10 +1,12 @@
-### Next version
+<a name="v0.16.0"></a>
+### v0.16.0 - 2020-06-20
 #### Major feature: composite patterns
 It's now possible to use logical operators on patterns.
 For example:
 `!/txt$/` : files whose name doesn't end in "txt"
 `carg|c/carg` : files whose name or content has "carg"
 `(json|xml)&c/test` : files containing "test" and whose name fuzzily contains either "json" or "xml"
+The document contains other examples and precisions.
 
 <a name="v0.15.1"></a>
 ### v0.15.1 - 2020-06-12
diff --git a/Cargo.lock b/Cargo.lock
index 3f8a731..e0b45fe 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -61,7 +61,9 @@ checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
 
 [[package]]
 name = "bet"
-version = "0.3.3"
+version = "0.3.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "717a3e881f801bb9379813577ffe11e6b97662f1d81155cdc61e8f5271a4feb4"
 
 [[package]]
 name = "bitflags"
@@ -82,7 +84,7 @@ dependencies = [
 
 [[package]]
 name = "broot"
-version = "0.15.2-beta"
+version = "0.16.0"
 dependencies = [
  "bet",
  "chrono",
diff --git a/Cargo.toml b/Cargo.toml
index f20964f..52c6415 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "broot"
-version = "0.15.2-beta"
+version = "0.16.0"
 authors = ["dystroy <denys.seguret@gmail.com>"]
 repository = "https://github.com/Canop/broot"
 documentation = "https://dystroy.org/broot"
diff --git a/website/docs/input.md b/website/docs/input.md
index e0990fc..89a3cfd 100644
--- a/website/docs/input.md
+++ b/website/docs/input.md
@@ -50,8 +50,8 @@ The caracters you use as operators and the parenthesis can be useful in patterns
 
 Most often you'll just type what feels natural and broot will select the interpretation which makes sense but you might be interested in a few rules:
 
-* parenthesis and operators in the second pattern part (parts being separated by `/`) are part of the patternC, which explains why `/(json|xml)` is interpreted as a regular expression. If you want to do a fuzzy search for a `|` in the name of your files, you'll need to have an explicit pattern mode : `nf/a|b` because `a|b` would search for files whose name contains either `a` or `b`. And to ensure an operator or closing parenthesis isn't interpreted as part of your pattern, just close it with a `/`.
-* broot interprets the left operand before the right one and don't interpret the second one if it looks useless. So if you want to search your whole disk for json files containing `abcd`, it will be faster to use `/json$/&c/abcd` rather than `c/abcd/&/json$/` which would look at the file name only after having scanned the content.
+* parenthesis and operators in the second pattern part (parts being separated by `/`) are part of the pattern, which explains why `/(json|xml)` is interpreted as a regular expression. If you want to do a fuzzy search for a `|` in the name of your files, you'll need to have an explicit pattern mode : `nf/a|b` because `a|b` would search for files whose name contains either `a` or `b`. And to ensure an operator or closing parenthesis isn't interpreted as part of your pattern, just close it with a `/`.
+* broot interprets the left operand before the right one and doesn't interpret the second one if it's not necessary. So if you want to search your whole disk for json files containing `abcd`, it will be faster to use `/json$/&c/abcd` rather than `c/abcd/&/json$/` which would look at the file name only after having scanned the content.
 
 ## The verb invocation