From 84307a3881a8f7ca1c284a6cba0ef1783dc24e16 Mon Sep 17 00:00:00 2001
From: Peter Solnica <peter@solnica.online>
Date: Sun, 16 Jul 2023 09:01:58 +0200
Subject: [PATCH] Update changelog.yml

---
 changelog.yml | 54 +++++++++++++++++++++++++--------------------------
 1 file changed, 27 insertions(+), 27 deletions(-)

diff --git a/changelog.yml b/changelog.yml
index efaf9c2..ff071d3 100644
--- a/changelog.yml
+++ b/changelog.yml
@@ -1,11 +1,11 @@
 ---
-- version: unreleased
-  summary: 
-  date: 
+- version: 1.0.2
+  summary:
+  date: 2022-07-16
   fixed:
   - 'Allow nested settings to default to `Undefined` (fixes #158 via #161) (@emptyflask)'
-  added: 
-  changed: 
+  added:
+  changed:
 - version: 1.0.1
   date: 2022-11-16
   changed:
@@ -22,7 +22,7 @@
   - Restored performance of config value reads (direct reader methods as well as aggregate
     methods like `#values` and `#to_h`) to pre-0.16.0 levels (#149 by @timriley)
 - version: 0.16.0
-  summary: 
+  summary:
   date: 2022-10-08
   fixed:
   - Remove exec bit from version.rb (#139 by @Fryguy)
@@ -50,7 +50,7 @@
       Your usage of dry-configurable may be impacted if you have been accessing objects from `_settings` or the internals of `Dry::Configurable::Config`. `_settings` now returns `Dry::Configurable::Setting` instances, which contain only the details from the setting's definition. Setting _values_ remain in `Dry::Configurable::Config`.
   - Use Zeitwerk to speed up load time (#135 by @solnic)
 - version: 0.15.0
-  summary: 
+  summary:
   date: '2022-04-21'
   changed:
   - |-
@@ -83,7 +83,7 @@
   - "`Dry::Configurable::Config#update` will accept any values implicitly convertible
     to hash via `#to_hash` (#133 by @timriley)"
 - version: 0.14.0
-  summary: 
+  summary:
   date: '2022-01-14'
   changed:
   - Settings defined after an access to `config` will still be made available on that
@@ -94,7 +94,7 @@
     config values have been changed in the parent _will_ receive those config values.
     (#130 by @timriley)
 - version: 0.13.0
-  summary: 
+  summary:
   date: '2021-09-12'
   fixed:
   - Fixed `ArgumentError` for classes including `Dry::Configurable` whose `initializer`
@@ -122,7 +122,7 @@
       ```
   - "[BREAKING] Removed implicit `to_hash` conversion from `Config`. (#114 by @timriley)"
 - version: 0.12.1
-  summary: 
+  summary:
   date: '2021-02-15'
   fixed:
   - |-
@@ -149,40 +149,40 @@
     A custom cloneable setting value should provide its own `#initialize_copy` (used by
     `Object#dup`) with the appropriate logic. (@timriley in #102)
 - version: 0.12.0
-  summary: 
+  summary:
   date: '2020-12-26'
   fixed:
   - Setting values provided by defaults and/or pre-processor blocks are no longer
     accidentally memoized across instances of classes including Dry::Configurable
     (#99) (@timriley & @esparta)
-  added: 
+  added:
   changed:
   - 'Instance behavior is now prepended, so that if you have your own `initialize`,
     calling `super` is no longer required (see #98 for more details) (@zabolotnov87)'
   - Switched to equalizer from dry-core (@solnic)
 - version: 0.11.6
-  summary: 
+  summary:
   date: '2020-06-22'
-  fixed: 
-  added: 
+  fixed:
+  added:
   changed:
   - 'A meaningful error is raised when the extension is included more than once (issue
     #89 fixed via #94) (@landongrindheim)'
   - Evaluate setting input immediately when input is provided. This allows for earlier
     feedback from constructors designed to raise errors on invalid input (#95) (@timriley)
 - version: 0.11.5
-  summary: 
+  summary:
   date: '2020-03-23'
   fixed:
   - 'When settings are copied or cloned, unevaluated values will no longer be copied.
     This prevents unintended crashes when settings have constructors expecting a certain
     type of value, but that value is yet to be provided (Fixed via #87) (@timriley)'
-  added: 
+  added:
   changed:
   - 'A meaningful error is raised when the extension is included more than once (issue
     #89 fixed via #94) (@landongrindheim)'
 - version: 0.11.4
-  summary: 
+  summary:
   date: '2020-03-16'
   fixed:
   - "`Config#update` returns `self` again (issue #60 fixed via #92) (@solnic)"
@@ -191,26 +191,26 @@
     settings that are yet to have a value applied (e.g. when they have a constructor
     that expects a value to be present) (@timriley)"
 - version: 0.11.3
-  summary: 
+  summary:
   date: '2020-02-22'
   fixed:
   - 'Retrieving settings by a string name works again (issue #82) (@waiting-for-dev)'
-  added: 
-  changed: 
+  added:
+  changed:
 - version: 0.11.2
-  summary: 
+  summary:
   date: '2020-02-20'
   fixed:
   - Warning about redefined `Setting#value` is gone (@solnic)
 - version: 0.11.1
-  summary: 
+  summary:
   date: '2020-02-18'
   fixed:
   - 'You can use `:settings` as a config key again (issue #80) (@solnic)'
   - Setting value is lazy-evaluated now, which fixes some cases where a constructor
     could crash with a `nil` value (@solnic)
-  added: 
-  changed: 
+  added:
+  changed:
 - version: 0.11.0
   date: '2020-02-15'
   summary: 'Complete rewrite of the library while keeping the public API intact. See
@@ -224,8 +224,8 @@
   summary: YANKED because the change also broke inheritance for classes that used
     `configured` before other classes inherited from them.
   date: '2020-01-31'
-  fixed: 
-  added: 
+  fixed:
+  added:
   changed:
   - Inheriting settings no longer defines the config object. This change fixed a use
     case where parent class that already used its config would prevent a child class