v0.11.0

What's Changed

• Update vault-ruby, Ruby 3.1+, etc for a 0.11.0 release by @chrisarcand in #152

Full Changelog: v0.10.0...v0.11.0

v0.10.0

What's Changed

• Added vault_encrypt_attributes! model method which allows callers to encrypt vault attributes without saving the model

New Contributors

• @haydengomes made their first contribution in #145
• @brandonc made their first contribution in #150

Full Changelog: v0.9.0...v0.10.0

v0.9.0

v0.9.0

IMPROVEMENTS

• Updated the vault dependency to v0.18.0 to support TLS v1.3.

v0.8.0

v0.8.0

IMPROVEMENTS

• Added Vault::MissingRequiredStateError to list of error types to be retried automatically in with_retries and updated vault gem minimum version requirement accordingly

v0.7.1

• Relaxed the dependency requirements for the gem to only depend on ActiveSupport, not the Rails meta gem, which allows applications using vault-rails to not require all of Rails as necessary transitive dependencies.

v0.7.0

v0.7.0 (October 27th, 2020)

IMPROVEMENTS

• Added support for the Vault Enterprise transform secrets engine, extending 'vault_attribute' with a 'transform_secret'
  hash that allows for format-preserving encryption [GH-102]

BUG FIXES

• Fixed an issue in newer versions of ActiveRecord where you could not access an encrypted attribute after a 'destroy'
  (for instance, as part of a dependant: :destroy chain). Attributes are now decrypted before a destroy, as a result. [GH-110]
• Fixed a regression where attributes being assigned to nil would be not respected [GH-107]

BREAKING CHANGES

• Dropped support for Rails 4.2 [GH-108]

v0.6.0

v0.6.0 (May 11th, 2020)

IMPROVEMENTS

• Added support for Rails 5.2+ (including 6.0+)
• Added ciphertext prefixes in development/test environments to more closely resemble production environments
• Added single-decrypt functionality to allow clients to request individual attributes rather than exposing an entire model with one call

BREAKING CHANGES

• Ciphertext prefixes may break development environments for some users. If this occurs, a restart may fix the issue. Feel free to let the maintainers know if this is not the case.

v0.5.0

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]

Version 0.4.0

Merge pull request #51 from hashicorp/kerrizor/update-changelog

Update CHANGELOG.md ahead of v0.4.0 release