the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting (#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 to conda shell.posix command (#14398)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)

the local version is empty. • The version part is then split into components at . and _. • Each component is split again into runs of numerals and non-numerals • Subcomponents containing only numerals integers. • Strings are converted to lowercase, with special treatment for dev and post. • When a component starts with a letter, the fillvalue 0 is inserted to keep numbers and strings in phase, resulting switching the solver? In short: to make conda faster and more accurate. A “solver” is the core component of most package managers; it calculates which dependencies (and which version of those dependencies)