# Change Log

## 0.0.18

* \#57. Include existing manifests' dependencies in resolution.

* Permit the update action even with a changed specfile.

## 0.0.17

* Use a pure-Ruby implementation of tar/gz. Helps with Windows support, since
  Windows boxes are less likely than *NIX boxes to have the `tar` executable.

* Fix an issue where the chef site source considers uncached manifests to be
  cached, and skips caching them, causing the install action to fail.

* Fail fast if the resolver produces an inconsistent resolution. It is a known
  issue that the resolver will sometimes (deterministically, not randomly)
  produce an inconsistent resolution when performing an update action (#57).
  Start debugging this by failing fast at this point and spitting out gobs of
  debug-level log details.

## 0.0.16

* Recache site-sourced dependency metadata per each run.

* \#46. Always install.

* \#53. Abstract versions & requirements from rubygems.

* Own the install path. Recreate it on each install.
    WARNING: If you have your own content in the install path, it will be deleted without mercy.

## 0.0.15

* Rewrite the README.

* \#44, \#49. Better updating of cached git sources without using local merges.

## 0.0.14

* \#39 Fixes a regression induced by using `git reset --hard SHA`.

## 0.0.13

* \#36 Fixes an issue where, if a dependency has a git source (the upstream), and the upstream is updated,
    then attempting to update that dependency in the local resolution would not update that dependency so
    long as that git source were cached (@databus23).

* More immediate detection of, and better error messages for, cases of blank dependency or manifest names
    or cases of names that are otherwise insensible, such as names that are untrimmed.

## 0.0.12

* Fixes an issue where, if a dependency has a git source with a ref, re-resolving may fail.

## 0.0.11

* Fix a regression where the cli command "version" failed.

## 0.0.10

This release focuses on refactoring some of the internals. There are no functional changes.

## 0.0.9

* \#11 Fixes a problem where, if the repo is in a path where a component has a space, attempting to resolve a
    site-sourced dependency fails.

## 0.0.8

* A `version` task.

* A change log.

* \#10 Fixes the problem with bouncing the lockfile when updating, when using a git source with the default ref.

## 0.0.7

* \#8 Add highline temporarily as a runtime dependency of `librarian` (@fnichol).
  When the project is split into `librarian` and `librarian-chef`, the `chef` runtime dependency will
    be moved to `librarian-chef`. If the project is further split into a knife plugin, the dependency
    will be moved there.

## 0.0.6

* \#7 Show a better error message when a cookbook is missing the required metadata file.

* Miscellaneous bugfixes.

## 0.0.5

* \#4 An `init` task for `librarian-chef`.
  This task creates a nearly-blank `Cheffile` with just the default Opscode Community Site source.

* Automatically create the `cookbooks` directory, if it's missing, when running the `install` task.

* \#3 Add `chef` temporarily as a runtime dependency of `librarian` (@fnichol).
  When the project is split into `librarian` and `librarian-chef`, the `chef` runtime dependency will
    be moved to `librarian-chef`.

## 0.0.4

* A simple knife integration.
  This integration allows you to specify a `librarian-chef`-managed tempdir as a `cookbook_path`.
  This is useful to force knife only to upload the exact cookbooks that `librarian-chef` knows
    about, rather than whatever happens to be found in the `cookbooks` directory.

## 0.0.3

* Miscellaneous bugfixes.

## 0.0.2

* An optional `:path` attribute for `:git` sources.
  This allows you to specify exactly where within a git repository a given cookbook is to be found.

* A full example of a Cheffile and its usage in the readme.

## 0.0.1

* Initial release.