Merge pull request #82 from hashicorp/release-notes-0.5.0

Bump version to 0.5.0 w/ changelog

CHANGELOG.md

@@ -1,6 +1,23 @@
 # Vault Rails Changelog
 
+## v0.5.0 (June 20th, 2019)
+
+IMPROVEMENTS
+
+- Added support for Vault Transit derived keys with the `:context` option. [GH-78]
+- Added a `:default` option to `vault_attribute`. [GH-83]
+
+BREAKING CHANGES
+
+- Dropped support for Ruby < 2.4, Rails < 4.2. [GH-79]
+- Null and empty types were previously deserialized to an empty JSON object (`{}`). They will now be properly deserialized as `null`, empty string (`""`), and so on. To preserve the old behavior, add `default: {}` to JSON-serialized attributes. [GH-81]
+
+BUG FIXES
+
+- Fixed uniqueness of generated key for in-memory operations. [GH-80]
+
 ## v0.4.0 (November 9, 2017)
+
 - Update supported Ruby and Rails versions [GH-50]
   - Ruby
     - Added 2.4.2

README.md

@@ -191,16 +191,22 @@ person.ssn # Vault communication happens here
 # => "123-45-6789"
 ```
 
-#### Automatic serializing
+#### Serialization
+
 By default, all values are assumed to be "text" fields in the database. Sometimes it is beneficial for your application to work with a more flexible data structure (such as a Hash or Array). Vault-rails can automatically serialize and deserialize these structures for you:
 
 ```ruby
 vault_attribute :details,
-  serialize: :json
+  serialize: :json,
+  default: {}
 ```
 
+It is recommended to set a default matching type that you're serializing.
+
 - **Note** You can view the source for the exact serialization and deserialization options, but they are intentionally not customizable and cannot be used for a full object marshal/unmarshal.
 
+##### Custom Serializers
+
 For customized solutions, you can also pass a module to the `:serializer` key. This module must have the following API:
 
 ```ruby

lib/vault/rails/version.rb

@@ -1,5 +1,5 @@
 module Vault
   module Rails
-    VERSION = "0.4.0"
+    VERSION = "0.5.0"
   end
 end