conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is CONDA_OVERRIDE_WIN usage. (#14443 via #14450) Bug fixes • Merge overlapping glob build specs instead of raising Incompatible component merge. (#11612) • Fix a bug when invalid values are being passed env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is environment setup 5. When you are ready to submit a change, create a new pull request so that we can merge your changes to our repository. Issue sorting Issue sorting is how we filter incoming issues and PYPY map import_module(name) dicttoolz Functions merge(*dicts, **kwargs) Merge a collection of dictionaries merge_with(func, *dicts, **kwargs) Merge dictionaries and apply function to combined val- ues

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out

conflicts between configurations arise, the following strategies are employed: • Lists - merge • Dictionaries - merge • Primitive - clobber Precedence The precedence by which the conda configuration is env create if the environment file is missing. (#11883) • Stop using toolz.dicttoolz.merge and toolz.dicttoolz.merge_with. (#12039) • Add support for incremental repodata.json updates with --experimental=jlap not to the whole code base at once. • Automatically build the conda package upon the successful merge into the master branch and upload it to the conda-canary channel on anaconda.org. To try conda out