0.8.0

Breaking

• Support for Ruby 2.0, 2.1 and 2.2 has been dropped, the minimum supported
  Ruby version is now 2.3.
  David Rodríguez

Enhancements

• Use Array#- in unwind logic, since it performs better than Array#&, so it
  speeds up resolution.
  Lukas Oberhuber

• Allow specification provider to customize how dependencies are compared when
  grouping specifications with the same dependencies.
  David Rodríguez

Bug Fixes

• None.

0.7.0

Breaking

• Support for Ruby 1.8.7 and 1.9.3 has been dropped, the minimum supported
  Ruby version is now 2.0.
  Samuel Giddins

Enhancements

• Circular dependency errors include the full (shortest) path between the
  circularly-dependent vertices.
  Samuel Giddins

Bug Fixes

• None.

0.6.6

Enhancements

• Improve performance of Vertex#path_to?.
  Samuel Giddins

• Allow customization of string used to say that a version conflict has occurred
  for a particular name by passing in the :incompatible_version_message_for_conflict
  key when constructing a version conflict message with trees.
  Samuel Giddins

Bug Fixes

• None.

0.6.5

Enhancements

• Improve performance of recursive vertex methods.
  Samuel Giddins

Bug Fixes

• None.

0.6.4

Enhancements

• Reduce memory usage during resolution by making the Vertex#requirements
  array unique.
  Grey Baker
  Jan Krutisch

Bug Fixes

• None.

0.6.3

Enhancements

• None.

Bug Fixes

• Handle the case where an unwind occurs to a requirement that directly caused
  the current conflict but could also have been unwound to directly from
  previous conflicts. In this case, filtering must not remove any possibilities
  that could have avoided the previous conflicts (even if they would not avoid
  the current one).
  Grey Baker

0.6.2

Enhancements

• None.

Bug Fixes

• Insist each PossibilitySet contains contiguous versions. Fixes a regression
  where an older dependency version with identical sub-dependencies to the
  latest version may be preferred over the second-latest version.
  Grey Baker

0.6.1

Enhancements

• None.

Bug Fixes

• Allow the set of dependencies for a given possibility to change over time,
  fixing a regression in 0.6.0.
  Samuel Giddins

0.6.0

Breaking

• Objects returned by dependencies_for and passed to resolve must properly implement
  both == and eql?, such that they return true when they exhibit the same behavior in
  requirement_satisfied_by?.

Enhancements

• Speed up dependency resolution by considering multiple possible versions of a
  dependency at once, grouped by sub-dependencies. Groups are then filtered as
  additional requirements are introduced. If a group's sub-dependencies cause
  conflicts the entire group can be discarded, which reduces the number of
  possibilities that have to be tested to find a resolution.
  Grey Baker
  Samuel Giddins
  #69

• Check for locked requirements when generating a new state's possibilities
  array, and reduce possibilities set accordingly. Reduces scope for erroneous
  VersionConflict errors.
  Grey Baker
  #67

• Add VersionConflict#message_with_trees for consumers who prefer a more verbose
  conflict message that includes full requirement trees for all conflicts.
  Samuel Giddins

Bug Fixes

• Improve unwinding by considering previous conflicts for the same dependency
  when deciding which state to unwind to. Previously, prior conflicts were
  stored in a hash indexed by their name, with only the most recent conflict
  stored for each dependency. With this fix, Molinillo can resolve anything
  that's thrown at it. 🎉
  Grey Baker
  #73

• Only raise CircularDependency errors if they prevent resolution.
  Ian Young
  Grey Baker
  #78

• Consider additional (binding) requirements that caused a conflict when
  determining which state to unwind to. Previously, in some cases Molinillo
  would erroneously throw a VersionConflict error if multiple requirements
  combined to cause a conflict.
  Grey Baker
  #72

• Consider previous conflicts when determining the state to unwind to. If a
  previous conflict, for a different dependency, is the reason we ended up with
  the current conflict, then unwinding to a state that would not have caused
  that conflict could prevent the current one, too.
  Grey Baker
  #72

0.5.7

Enhancements

• None.

Bug Fixes

• Keep a stack of parents per requirement, so unwinding past a swap point that
  updated the parent of the requirement works.
  Samuel Giddins
  bundler#5425