3.0.2 Make Hashie >= 4.0 optional

Some systems have dependencies that limit Hashie to < 4.0. So this release will use the quiet method from 4.0 or if greater if available.

What's Changed

• Make Hashie >= 4.0 optional by @shawnstephens in #33

New Contributors

• @shawnstephens made their first contribution in #33

Full Changelog: 3.0.1...v3.0.2

3.0.1

What's Changed

• bump hashie requirement to account for Mash.quiet by @zackse in #32 (thanks to @zorab47)

Full Changelog: 3.0.0...3.0.1

3.0.0

What's Changed

• Revert to Hashie::Mash-based implementation by @zackse in #31

The 2.x implementation via Hashie extensions was incomplete and removed some behavior that consumers had come to rely on, namely chained method calls. This changeset restores the Hashie::Mash implementation from 1.0.0.

Full Changelog: 2.0.0...3.0.0

2.0.0

What's Changed

• Return a hash with indifferent access rather than a Mash by @mboeh in #29
• Support Ruby 3.2 by @zackse in #30

Full Changelog: 1.0.0...2.0.0

1.0.0

What's Changed

• Switched to using Hashie::Mash for YAML parsing to address inconsistent behavior based on access pattern. This provides behavior that is more consistent, while remaining similar. It did not cause any tests to fail, but may be a breaking change depending on how you are using the gem, especially if you are merging hashes like Settings.top_key_hash.

Full Changelog: v0.2.4...1.0.0

0.2.4

What's Changed

• Support Ruby < 3.0.3 as we still support 2.7 for a few more months by @bak in #24

New Contributors

• @bak made their first contribution in #24

Full Changelog: v0.2.3...v0.2.4