5.4.0

New features

• Add configuration option environment to override the use of Rails.env (#356)

5.3.0

• Remove dry-validation from dependencies (#333)

5.2.0

New features

• Allow to use custom filename && directory name to store configs (#341)

Bug fixes

• Prevent name collision with private methods from ancestors (#351)

5.1.0

• Fix conflicts with Rails 7 active_support methods (#347)

5.0.0

BREAKING CHANGES

• No longer load deep_merge's monkey patch for Hash#deep_merge and Hash#deep_merge! (#342). If you rely on those methods and are not using Rails / Active Support, you can load the monkey patch via require 'deep_merge/deep_merge_hash'. This change fixes Rails 7.x support.

4.2.0

Bug fixes

• Remove use of method File.exists? to fix use in Ruby 3.0 (#318)

4.1.0

Bug fixes

• Only load Railtie integration if Rails::Railtie is defined (#319)
• Fix indentation warning in Ruby 3.1 (#322)

4.0.0

BREAKING CHANGES

• Rails versions < 5.2 are no longer supported (#316)
• Ruby versions < 2.6 are no longer supported (#316)
• Support HashSource and EnvSource instances in Config.load_files and Config.load_and_set_settings. (#315). There are a few subtle breaking changes:
  • Previously, Config.load_files (called from Config.load_and_set_settings) would call .to_s on each of its arguments. Now, this responsibility is defered to YAMLSource. In effect, if your application passes String or Pathname objects to Config.load_files, no changes are necessary, but if you were somehow relying on the .to_s call for some other type of object, you'll now need to call .to_s on that object before passing it to Config.
  • Before this change, Config.load_files would call uniq on its argument array. This call has been removed, so duplicate file paths are not removed before further processing. In some cases, this can cause differences in behavior since later config files override the values in earlier ones. In most cases, it's best to ensure that duplicate paths are not passed to Config.load_files.

3.1.1

Bug fixes

• Allow the use of unsafe YAML parsing features when using psych >= 4 (#306)

3.1.0

New features

• Evaluating ERB in YAML files can now be disabled with Config.evaluate_erb_in_yaml = false. The default value for this option is true for backwards-compatibility. (#303)