interactively query for license, suggest SPDX licenses (#1902) ...

Co-authored-by: Martin Nowak <code@dawg.eu>

add --deep flag to `dub build` ...

Allows to build all dependencies of a static library

Implemented recipe files for dub #2684 (#2685) ...

Co-authored-by: Jan Jurzitza <gh@webfreak.org>

support specifying --d-versions ...

Usually you should prefer using configurations and build types, but
sometimes, especially when wrapped in other build tools or when
supporting e.g. different target platforms on the same target
architecture and configuration, you may want to manually manage certain
versions.

Fix #2574: Suggest alternative spelling when a command is mistyped (#2593) ...

Co-authored-by: WebFreak001 <gh@webfreak.org>

Merge remote-tracking branch 'upstream/stable' into merge_stable

Make `dub run --root=x` default app CWD in dub CWD ...

Fix #2582

fix typo(s)

Merge remote-tracking branch 'upstream/stable' into merge_stable

reduce dependency on the working directory ...

Improves library API usage and bugs with the build generator

replace std.variant with std.sumtype (#2550) ...

Variant is quite big and runtime heavy, with sumtype we already cover
wrong type cases at compile time.

Implement --color=auto|always|never, fix #2410 (#2552) ...

* Implement --color=auto|always|never, fix #2410

Also improves error message output for unsupported --color values.

* fix compile error with certain D versions

Use a central build cache for all build artifacts ...

Currently the central build cache is not configurable,
but as most build artifacts end up in `~/.dub/packages/` anyway,
this will be a positive change for users.

Fixed dub init docs (#2537)

Improve dub init custom template docs

Replace all instances of mkdirRecurse with ensureDir ...

All usages actually want to ensure the directory is present,
and don't care about having a separation between existence check
and creation.

Move foreign code from global scope to dub.internal. ...

Avoids conflicting with the actual dub packages when working with dub as a library. Also, even if just by convention, it ensures that dependent code doesn't rely on this code as a public API.

Do not use Phobos' sumtype, use dyaml's versioned one ...

So that we can compile with older versions of the frontend,
currently v2.097 instead of v2.098.

Dub: Deprecate changing the rootPath ...

It's an essential part of the setup, and too many properties are derived
from it that we don't want to let the library user the ability to mess with it.

Commandline: Use inheritance, not a boolean, to control Dub initialization ...

The boolean was a breach of abstraction, as it was introduced
for a single sub-command. Instead, use inheritance, which
allows to keep that logic compartimentalized to the subcommand itself.

Use dscanner-config for `dub lint` ...

Keep all original commandline flags in case we want support them in
the future.

Fixes #1940

Support --temp-build also in `dub build` (#2428)

fix coloring for dub upgrade -s

Deprecate PackageManager.getFirstPackage ...

This function returns the 'first' package, which is very arbitrary.
Instead, always return the highest matching package for stable results.

Deprecate overrides: local-overrides.json, add-override, remove-override ...

As explained in the changelog, overrides were a solution to a system
with version-only dependencies, which is long gone.

Trivial: Improve 'dub list' description

Use configy library to parse dub.json file ...

This will provide a vastly superior UX to the users:
- They will be warned about typos;
- The type information provided will be more accurate and always include file/line infos
  (e.g. no more 'Invalid SemVer versions');
- We can expose a better recipe struct to library users on the long run,
  by separating the actual data DUB uses from what it reads;
- We can be more descriptive about errors / intent, for example by using `SetInfo`;

Dependency: Deprecate path/repository setters ...

There is no real use case for changing a dependency in place,
instead we better let the user overwrite the dependency itself.

Forward flag `--color={on,off}` to compiler calls (#2382) ...

When the user sets the color mode explicitly,
we forward it to the compiler for consistency,
while making sure it doesn't impact the build cache ID.

Rename CLI flag --colors to --color any D code symbols accordingly