Make the describe() API strongly typed.

Add Dependency.versionSpec property.

Fix equality comparison of identical versions with different meta data.

Use booleans instead of strings to represent version range limits. ...

Also disallows specifying invalid version ranges as strings.

Fix limit conditions when merging dependency version ranges. ...

When merging a dependency ">=A <B" with a dependency that matches B exactly, the resulting dependency was ">=B <=B" instead of ">=B <B", thus erroneously matching B.

Apply patch by ketmar: remove comma expressions and fix property syntax. ...

Also contains two minor additional style fixes.

Avoid catching Error instances in various places. See #443.

DFix the code

Add an early out for invalid child configurations in the dependency resolver. Fixes #405. ...

Previous behavior could cause exponential run time.

Missing format()

Improve some package upgrade related messages.

Fix optional dependencies being always downloaded with the new dependency resolver. Fixes #359.

Removed trailing whitespace

Converted line endings from CRLF to LF

Update unit test for new path based dependency behavior.

Fix path based dependencies. See #282 and #253.

Fix detection of already visited nodes in DependencyResolver. See #280. ...

Fixes a stack overflow for package graphs with cycles.

Properly support path based version selections.

Let "*" match any version or branch. Fixes #151.

Let Dependency.toString() also contain the optional/path properties. ...

versionString is changed into a public property to support the use cases where only the version range is expected.

Fix resolution of optional and path based dependencies.

Add command line interface for managing package overrides.

Move DependencyResolver to its own module and reorder Version<->Dependency.

Fix 64-bit compilation.

Compile fix for DMD 2.064.

Implement a new dependency resolution algorithm with support for selections. ...

The new algorithm is completely rewritten to be able to find any valid combination of dependencies/versions. The old one could error out in cases where a valid dependency tree could have been built. Now the current selections are also taken into account when invoking without UpdateOptions.upgrade.

Some side changes:
 - Comparing branch versions is allowed now to enable sorting the full set of versions of a package
 - DependencyGraph and RequestedDependency have been removed

Build fix.

Fixing 'dub fetch xyz --version=a.b.c', the latest version was fetched instead of the specified. ...

The problem was that Dependency("1.0.0") != Dependency("==1.0.0") or Dependency(Version("1.0.0")). Similar to the branches, not specifying a comparison operator assumes identical version required.

Preparing dub select command. dub select will select the currently used versions and write them to a file, so that dub can later use this information to rebuild this exact state. This will also be used to override dependencies with either branch versions or not matching versions (to resolve conflicts). (All of this if to be implemented). ...

Other changes:
- Added Version.UNKNOWN, which could be later used for undetermined package versions instead of ~master.
- Added Dependency to/fromJson.
- Added Dependency alias "*" for ">=0.0.0".

Following rubygems version specification for approximate version more closely.