Adding an example for PromisedKeysNotInContextError
Releasing version 0.3 with expects and promises
Added ability to set an error code on the context in the event of failure
Thinking an options hash might be better in this instance, so that you can specify which is the message and which is the error. Just passing both in as a method call seems wonky, although just calling fail! with only a message (as usual) is still supported.
Merge pull request #35 from jenpayne/add_error_code_to_failure_context

Added ability to set an error code on the context in the event of failur...
Using the RSpec provided assertion for boolean field
Making a `map` block prettier and easier to read
No need to pass the default arguments
Cleaning up the Context specs a bit

Separating the assertions in the spec with a line break.
Adding an assertion for the error_code when it was not
provided.
Test against more recent ruby versions
Merge pull request #38 from padi/update_travis

Test against more recent ruby versions
Adding documentation for error codes in the context
Preparing the release 0.3.1
Fixing documentation and using separate args for error_code
Don't need to ask if actions is an array
Merge pull request #40 from padi/dont_ask_if_array

Don't need to ask if actions is an array
Moving the `promises` and `expects` accessors to Context

The concept of `self.order` does not make much sense. Where did that 
variable or attribute reader come from? It makes a ton more sense to
ask the Context itself to provide the accessors for the promised and
expected keys.
Updating README with context accessor changes
Updating README with 0.3.3 changes
Update ruby patch version

Since 2.1.2 was released this month. Noticed it just now. https://www.ruby-lang.org/en/news/2014/05/09/ruby-2-1-2-is-released/