# 0.2.7

* **BUGFIX:** Handle falsy values correctly in `ValidationError`. Thanks to [larose](https://github.com/larose).
* Other code cleanups. Thanks again to [larose](https://github.com/larose).

# 0.2.6

* **BUGFIX**: An `undefined` instance is no longer tested as if it’s an `object`. Fixes a crash that occurred if the instance was `undefined` and the schema used a `required` keyword. Thanks to [emschwartz](https://github.com/emschwartz).

# 0.2.5

* **BUGFIX**: Explicitly specifying an unrecognized top-level `$schema` (something other than JSON Schema Draft 4) now returns a standard JaySchema error instead of dumping you out to a stack trace. Thanks to [schimmy](https://github.com/schimmy).
* **BUGFIX/ENHANCEMENT**: You can now specify the “current version” `$schema`. Previously the only schema you could explicitly specify was the Draft 4 schema. In other words, any the following at the top of a schema def will work:
      * `{ "$schema": "http://json-schema.org/draft-04/schema#" }`
          * this has always been supported
      * `{ "$schema": "http://json-schema.org/schema#"}`
          * this is new and will use the draft-04 schema rules
      * (no `$schema` value)
          * this has always been supported and will use the draft-04 schema rules

  Thanks to [schimmy](https://github.com/schimmy).

# 0.2.4

* **BUGFIX**: Schema ID URLs that have `..` in them are normalized and can now be used. Thanks to [alexbirkett](https://github.com/alexbirkett).

* **BUGFIX**: Fixed a hang/timeout when a loader function is provided, but no external schemas are loaded. Thanks to [alexbirkett](https://github.com/alexbirkett).

# 0.2.3

* **BUGFIX**: Better logic for validating the `hostname` format. IPv4 addresses are no longer recognized as hostnames. Thanks to [k7sleeper](https://github.com/k7sleeper).

# 0.2.2

* **BUGFIX/ENHANCEMENT**: Instances and schemas which do not have the `Object` prototype are now supported. Thanks to [adrianlang](https://github.com/adrianlang).

# 0.2.1

* **BUGFIX/ENHANCEMENT**: Properly support the Draft v3 `date` and `time` formats.

# 0.2.0

* :exclamation: — **[BREAKING CHANGE]** In a few rare cases the async version of `validate()` returned a bare error object. The async version of `validate()` is documented to return an *array* of error objects, or `undefined` if there are no errors. It now behaves as documented.
* There’s a small possibility that this could break code that depends on the old, quirky, behavior. Therefore the version number has been incremented so  existing projects that depend on the 0.1.x behavior will not be unexpectedly upgraded, as long as you are following [best practices](https://npmjs.org/doc/json.html#Tilde-Version-Ranges) for `package.json` dependencies.
    * A good dependency specification is: `"jayschema": "~0.2.0"`, or `"jayschema": "~0.1.6"` if you still need the old behavior.
    * `"jayschema": "0.2.x"` and `"jayschema": "0.1.x"` would also work.

# 0.1.6

* **BUGFIX**: Fix a race condition when doing multiple simultaneous validations. Previously, if you were doing several validations and they all referred to the same external schema (that needs to be loaded using a loader function), some of the validations could fail. This has been fixed.
* **BUGFIX**: Fix a potential failure to resolve a URI that affected Node > 0.9.1.
* **ENHANCEMENT**: Improved compatibility with Node 0.6.x. Versions 0.6.6 and higher are supported. Previously the main library worked, but the tests and command-line utility would fail.
* **CHANGE/BUGFIX**: The sample HTTP loader utility (`JaySchema.loaders.http`) was failing to load from HTTPS URLs on Node > 0.9.1. It can once again load from SSL sources, but note that it does not attempt to validate the SSL certificate. If you need more sophisticated HTTPS functionality, consider writing your own loader using something like [request](https://github.com/mikeal/request), which gives you much more control.

# 0.1.5

* **FEATURE**: You can now query to see if a schema has been registered, by calling the `isRegistered(id)` method of the `JaySchema` class.

# 0.1.4

* **BUGFIX**: More consistent checks for registered schemas. Fixes issue #2: the `register()` method return value was showing some schemas missing, when in fact, they were registered.

# 0.1.3

* **BUGFIX**: The `getMissingSchemas()` method is fixed. It was showing some schemas as missing, when in fact, they were registered.
* **FEATURE**: You can pass a string instead of a schema to the `validate()` function. If the string is the `id` of a registered schema, your instance will be validated against that schema.

# 0.1.2

* The `JaySchema.errors` object is now exposed. Authors of schema loaders may wish to use the `JaySchema.errors.SchemaLoaderError` to signal failure to load a requested schema.
* The included HTTP loader now works with HTTPS as well, and follows 3XX redirects.

# 0.1.1

* Nested `$ref`s which refer to other `$ref`s are now handled correctly.

# 0.1.0

* First non-beta release.

# 0.1.0-beta.5

* Updated test suite to include the new draft4 tests in JSON-Schema-Test-Suite.
* Better internal handling of schema registration.
* Fixed bugs related to using a URN schema id.
* Fixed a bug affecting the "multipleOf" keyword when using very small numbers.

# 0.1.0-beta.4

* Improved performance and reduced memory usage.
* Internal code organization clean-up.

# 0.1.0-beta.3

* Improved performance as indicated by profiling.

# 0.1.0-beta

* Updated version number to 0.1.0-beta, as 0.1.0 is the likely version number of the first non-beta release.
* :new: — Support for the `format` keyword. All formats defined in the spec are supported: `date-time`, `email`, `hostname`, `ipv4`, `ipv6` and `uri`.

# 0.0.1-beta

* :exclamation: — **[breaking change]** The `validate()` method no longer auto-downloads schemas from HTTP. If you rely on this functionality, the following code is equivalent:
    * Old code (with auto HTTP loading): `var js = new JaySchema();`
    * New equivalent: `var js = new JaySchema(JaySchema.loaders.http);`
* :new: — **[major feature]** Customizable loader for external schemas. You can provide a custom loader that will be called when an external schema is referenced. This allows you to reference schemas that are stored in a database, downloaded from HTTP, or by any other method you choose.
* Upgraded to beta—no further breaking changes are planned for this release.

# 0.0.1-alpha

* :new: — Initial release