dependency update (MacOS BigSur only)

Please note that the linux build seems to fail on my machine as cargo is unable to download anything from crates.io. Thus for now I only provide binaries for MacOS.

For linux builds, please have a look at older releases.

Fix Homebrew release; update minor dependencies

### V4.0.9: Update brew package description; update dependencies

* it's necessary to depend on `gpgme` instead of just `gnupg` for the tool to work on MacOS by default

### V4.0.7: --partial <file> support for template engines

You can now pass partial templates for use in liquid and handlebars directly using the
'--partials=templatepath...' flag in the 'substitute' subcommand.

### V4.0.6: Dependency Update

* Assure writes to a single unique output file will overwrite its complete content during substitution.
    * Previously, if you would write less than the original file size, parts of the previous content may still be present.

### V4.0.5: Dependency Update

* upgrade all dependencies to the latest version

### V4.0.4: Dependency Update

* upgrade all dependencies to the latest version

### V4.0.3: Dependency Update

* upgrade all dependencies to the latest version

### V4.0.2: Fixes and improvements

* add the '--no-stdin' flag to `sy process`. It allows to prevent it from blocking on reading from
  stdin in certain situations. Previously, one would have to provide some stdin like `echo '{}' | sy process ...`.

### V4.0.1: Fixes and improvements

This release contains some minor fixes and improvements, as well as a lot more documentation.

#### More documentation

 * [x] Documentation for
   * [x] [substitute][substitute]
   * [x] [process][process]
   * [x] [extract][extract]
   
[substitute]: https://share-secrets-safely.github.io/cli/tools/substitute.html
[process]: https://share-secrets-safely.github.io/cli/tools/process.html
[extract]: https://share-secrets-safely.github.io/cli/tools/extract.html
   
#### Git-based installation

 * [x] **getting-started** - a repository with all you need to start using a _sheesy_ vault in teams.
   * See https://github.com/share-secrets-safely/getting-started
   
### V4.0: Liquid as substitution-engine and a program per sub-command

#### Switch to Liquid templating engine

When looking at helm it becomes evident how much more filters would be needed to effectively
adjust yaml files.

Handlebars was a nice try, yet it only shows that filters are what makes a language powerful.
Fortunately it's still time to change, so let's swap handlebars with [liquid][liquid].

 * [x] add liquid 
 * [x] add handlebars
 * [x] add base64 filter to _liquid_

[liquid]: https://shopify.github.io/liquid/

#### Sub-Commands as standalone programs

Even though the main binary should by `sy` as before, the code should be structured to
provide `cli` versions of the respective subcommand, e.g. `vault-cli`.
That way, people can also use special-purpose sub-programs directly without having
a binary that contains all the other cruft.

This can be useful to make `pass` standins more approachable, and also build custom
`sy` binaries with just a sub-set of the functionality (for example, without `pass`
stand-in capability).

 * [x] binary for sheesy-
   * [x] hub
   * [x] vault
   * [x] process
   * [x] substitute
   * [x] extract

#### Non-Functional: Move to Organization

In order to get the project where it is supposed to be, it can't be in my
user's space. We will have multiple repositories and hopefully some more contributors.

The new organization should have the following repositories:

 * [x] **CLI** - the 'sheesy' command-line interface
 
### V3.3: Value extraction and basic trust controls

#### Improved UX and basic Web of Trust controls

Having spend some time reading up on the issue, and having realized that there is a reason
the 'Web of Trust' model as implemented by GPG/PGP are not particularly wide-spread for a reason,
for adoption, there should be a way to turn it off and delegate trust checking to external sources
(_like [keybase.io][keybase]_).

Also given the way the vault is typically used, we should disable it by default, and make enabling
it optional to more advanced teams.

 * [x] Configure web-of-trust options on per-partition basis and use that when encrypting.
 * [x] Option to auto-import keys when encrypting resources, which is enabled by default.
 * [x] Don't fail when listing recipients whose keys are not in the keychain.
 
[keybase]: https://keybase.io

#### The `extract` subcommand

The `extract` capability makes it feasible to store secrets in structured files
like YAML or JSON, as it allows to extract pieces of data in various ways.
Think basic `jq` but with native support for YAML files.

## V3.2: Master-Merger

The `merge` subcommand allows to combine JSON or YAML files.
This is useful to partition context and data according to your needs, yet use
all of the values in combination for substitution.
It is particularly useful if some of that content was just decrypted from a vault.

 * [x] **The merge sub-command**
   * [x] with conflicts
   * [x] with overwrite rules
   * [x] move keys to root level before merging
   * [x] insert keys at given value while merging for
     * [x] object paths, e.g `a.b.c` or `a/b/c`
     * [x] for array paths e.g. `a.0.c.1` or `a/0/c/1`
   * [x] merge complete environment into data, or whatever matches the given glob
   * [x] set individual values, simpy via 'a/b/c=42' or 'a.b.0=30'
 * [x] control the escape characters to allow passwords to be escaped properly, as needed, depending on the output format.
       Otherwise there is the chance of producing invalid YAML.

 * **improvements to substitute**
   * [x] `--verify` - try to decode substituted values and fail on error

 * **general improvements**
   * [x] Unify naming scheme of all deployables to make curling code easier
   * [x] find a better name for merge, given that merging is just a side-effect.
      With the action driven interface, it can do pretty much everything on the data
      it has so far. Some commands effect the merging, some pull out and/or print data.
      That way, extract is not a separate subcommand.
      
## V3.1: Substitution-Superpowers

Make it easy to generate property-sets by merging structured files together, and
make said context available to a `handlebars` powered engine to perform substitutions.

This allows to bring together context owned by various entities into a single aggregated
one, with the possibility for later contexts to override earlier ones.

With this capability, it's also possible to substitute secrets into files, for example
like this: `sy sub base.json sub/ours.yaml <(sy vault show secret.yaml) < deployment.yml | kubectl apply -f -`.

Read more [in the documentation](https://share-secrets-safely.github.io/cli/tools/substitute.html).

## V3.0: Support for Partitions

Partitions are just another vault with individual config, but operations on vaults are
aware of partitions. This allows sharing of keys for example, and alters the way
vaults are displayed when showing them.

### Features

 * **add** partitions and **remove** them
 * **initialize new vaults** with **partitions** in mind
 * **show recipients** per **partition**

### Improvements
 * Allow `sy vault` to operate anywhere with a `.gpg-id` file, like pass.
 * Strong validation of the vault configuration to assure consistency

### Breaking Changes

 * `vault --vault-id` is now `vault --select`

## V2.0: Better user experience and documentation

Besides the many improvements, you will also find [a complete book][book] about
the capabilities so far!

We also [sign our binaries][signatures] from here on, and make them available [via *homebrew*][install].

[signatures]: https://share-secrets-safely.github.io/cli/installation.html#via-a-hrefhttpsgithubcombyronshare-secrets-safelyreleasesreleasesa
[install]: https://share-secrets-safely.github.io/cli/installation.html#via-homebrew-osx-and-linux
[book]: https://share-secrets-safely.github.io/cli

### Improvements

 * `vault list` now produces precise URLs.
 * `vault remove` can remove resources from the vault.
 * `vault recipient add` now signs and re-exports added fingerprints to make
   recipient verification part of adding them, and help build a *Web of Trust*.
 * `vault recipients remove` removes recipients and re-encrypts the vaults content.
 * `vault recipient add` also adds recipients which are only in your gpg keychain.
    Previously it would always require an exported public key in the right spot.
 * `vault recipient add --verified` allows to add any recipient by name, but requires
    you to assure you are able to encrypt for that recipient.
 * `vault add` now creates sub-directories automatically.
 * `vault edit` now tries to encrypt before launching the editor.
 * `vault add :something` with a tty as standard input will open an editor automatically.

### Breaking Changes

The breaking change requiring a major version increment is changes to the `sy-vault.yml` file.

 * The `at` field is now called `secrets`
 * `recipients` and `gpg-keys` paths are no relative to the `sy-vault.yml` file, not relative to the
   `secrets` directory.
 * The '--at/-a' flag of `sy vault` is now `--secrets-dir-dir/-s`
 * `recipients add` will now require fingerprints unless `--verified` is specified.

These improvements make handling paths consistent and less suprising.

## V1.0.1: The very first release - with a new name!

`s3` now officially is `sy` on the command-line, and spelled `sheesy`. Crates
were renamed accordingly, too.

## V1.0: The very first release!

This is the first usable version, providing only the minimal amount of features.
A lot of the value contained is a fully automated system for quality assurance
and deployment, which will help keeping the releases coming.

 * [x] **setup rust workspace for clear dependency separation**
 * [x] **setup CI for linux and OSX**
 * [x] **standalone deployables without additional dependencies for**
   * [x] OSX (static binary) - _just gettext is still dynamically linked :(_
   * [x] MUSL Linux
 * [x] **shell completions**
 * [x] **complete a happy journey with**
   * [x] initialize a new vault
   * [x] add contents
   * [x] support for multiple vaults
   * [x] list vault contents
   * [x] decrypt vault contents
   * [x] edit vault contents
   * [x] add another user and re-encrypt vault content
 * [x] **installable from crates.io**
 * [x] **release binaries generated by travis for tags**

Dependency Update

In addition to updated dependencies, the extract and substitute sub-commands learned the --no-stdin flag.

--partial <file> support for template engines

You can now pass partial templates for use in liquid and handlebars directly using the
'--partials=templatepath...' flag in the 'substitute' subcommand.

A single bugfix in substitution engine

• Assure writes to a single unique output file will overwrite its complete content during substitution.
  • Previously, if you would write less than the original file size, parts of the previous content may still be present.

Security Update

• upgrade all dependencies to the latest version

A security update

In this release, all library dependencies were updated.

A highlight to mention is the Liquid template engine, which was updated to the very latest version. This removes the ability to check for the size of a string with `.size`, and replaces it with the size filter like this:` | size`.

v4.0.3 Security Update

Update of all dependencies to the latest version.

v4.0.2: Some more minor improvements

• add the '--no-stdin' flag to sy process. It allows to prevent it from blocking on reading from
  stdin in certain situations. Previously, one would have to provide some stdin like echo '{}' | sy process ....

v4.0.1: The first patch-release!

This release contains some minor fixes and improvements, as well as a lot more documentation.

More documentation

• Documentation for
  • substitute
  • process
  • extract

Git-based installation

• getting-started - a repository with all you need to start using a sheesy vault in teams.
  • See https://github.com/share-secrets-safely/getting-started