One function

object_merge in dynaconf/dynaconf

The author described this change as fix: keep sibling keys that share a dotted path leaf name (#1434). It counts as a record because the check below fails on the code as it stood at b56a831c0 and passes on ec3bc0940, with nothing else changed between the two runs.

Fix saved2026-07-29
Sharing licenceMIT · LICENSE
Change size+1 0

What the code was meant to do, written into the code itself as a docstring

Recursively merge two data structures, new is mutated in-place. :param old: The existing data. :param new: The new data to get old values merged in to. :param unique: When set to True existing list items are not set. :param full_path: Indicates the elements of a tree. :param list_merge: Methods to use to merge lists - merge: default merge behavior, i.e. (unique) concatenation - shallow: replace the top-most level list of the nested structure - deep: iteratively traverse the nested structure and replace the element in the list at the level specified by the full_path

The change

8383 # but the new value on the end of full path is the same
8484 if (
8585 existing_value is not None
86+ and len(full_path) == 1
8687 and old_key.lower() == full_path[-1].lower()
8788 and existing_value is value
8889 ):

The check that tells the two apart

failpass·tests/test_validators.py::test_sibling_key_sharing_leaf_name_survives_validation

Check file tests/test_validators.py, taken without changes from the fix and copied onto the older code, so the exact same check runs against both versions.

Origin and history

The code before itb56a831c0846b2a8e6d725afac4abf9ae50c9105
Broken version dated2026-07-29
Moduledynaconf.utils.__init__
Units changedobject_merge
Fingerprint960880de095cf3e3
Checked2026-08-18 by goldset/0.1

Every field above is generated by our program. None of it is written by hand.

Other bugs found in dynaconf/dynaconf