v1.10.6

Fixed

• Fix issues with rule name when top_namespace and namespace passed (issue #304 fixed via #432) (@RudskikhIvan)

Compare v1.10.5...v1.10.6

v1.10.5

Fixed

• Key maps no longer include duped keys when using inheritance (issues #428 #372 fixed via #429) (@solnic)
• Key validator and coercer no longer include duped keys when using parent schemas (via #430) (@solnic)

Compare v1.10.4...v1.10.5

v1.10.4

Fixed

• Once again reverting zeitwerk related changes that were included in 1.10.3 by an accident :( (@solnic)

Compare v1.10.3...v1.10.4

v1.10.3

Fixed

• Addressed regressions causing issues with handling sum types (see #419 and #423 fixed via #425) (@robhanlon22)

Compare v1.10.2...v1.10.3

v1.10.2

Fixed

• Fix value coercion for composed schemas (via #421) (@robhanlon22)

Compare v1.10.1...v1.10.2

v1.10.1

Changed

• Reverted zeitwerk-related changes that were included in 1.10.0 by an accident (@solnic)

Compare v1.10.0...v1.10.1

v1.10.0

Added

• Allow nested filled and value macro usage (via #412) (@robhanlon22)
• Support for more complex scenarios when composing schemas (via #420) (@robhanlon22)

Fixed

• Fix or messages for complex schemas (via #413) (@robhanlon22)
• Using filled with a constrained constructor type works as expected (via #416) (@robhanlon22)
• Fix types and key maps for composed schemas (via #415) (@robhanlon22)

Changed

• Freeze message hash (fixes #417 via #418) (@solnic)

Compare v1.9.3...v1.10.0

v1.9.3

Added

• Support anyOf composition in JSON schema output (@robhanlon22)

Fixed

• Allow composition of multiple ors (issue #307 fixed via #409) (@robhanlon22)

Compare v1.9.2...v1.9.3

v1.9.2

Fixed

• Fix loose JSON schemas for nested hashes (via #401) (@tomdalling)
• Correct spelling error 'mininum' to 'minimum' in json-schema extension (via #404) (@svenanderzen)

Changed

• [performance] YAML message backend allocates less strings (via #399) (@casperisfine)

Compare v1.9.1...v1.9.2

v1.9.1

Fixed

• Namespaced messages no longer crashes in certain scenarios (see dry-rb/dry-validation#692 fixed via #398) (@krekoten)

Compare v1.9.0...v1.9.1