Release 0.5.4

- `Assert::with_env` for setting environment variables

Release v0.5.3

- Support writing to `stdin`

Release 0.5.2

- Show stdout/stderr on exit code failures
- Show expected/got strings for output assertions

Release 0.5.1

- Reduce unnecesary rebuilds due to skeptic.

Release 0.5.0

This release includes
- Changing output asserts
  - `.prints` -> `.stdout().contains`
  - `.prints_exactly` -> `.stdout().is`
  - `.prints_error` -> `.stderr().contains`
  - `.prints_error_exactly` -> `.stderr().is`
- Add negative output assertions
  - `.stdout().isnt`
  - `.stdout().doesnt_contain`
- Output assertions are now anded together rather than replacing each
  other.

Add more Cargo metadata

- Now returns output information from assert calls

Auto merge of assert-rs#7 - Lindenk:ignore_output, r=killercup

Option to ignore output

Fixes assert-rs#6. I was thinking about whether to implement it as interpreting an empty string as matching any output, but I can see how many situations might call for explicitly expecting a command not to output (such as when testing a quiet mode). Is this alright?

Also, I think fuzzy matching should be a new issue. It would be a much different of an implementation than assert-rs#6.

Auto merge of assert-rs#5 - killercup:feature/apache+mit, r=killercup

Feature/apache+mit

- This adds the `assert_cli!` macro

- Rename `CliError::NoSuccess` to `CliError::WrongExitCode`