v0.7.3

Removed use of setImmediate to simplify use in browsers.

v0.7.2

This release corrects a regression. lockAcquiredTimeUnixMs, required for trustLocalTime configuration option to function correctly, is once again saved as required.

v0.7.1

Re-adds erroneously removed fencingToken property on an acquired FailOpen lock.

Reported problems:

This version does not store lockAcquiredTimeUnixMs property when trustLocalTime configuration options is selected. Upgrading to v0.7.2 resolves the problem.

v0.7.0

Using locks on DynamoDB tables that require a sort key is now supported.

Reported problems:

This version erroneously removed fencingToken property from an acquired FailOpen lock. Upgrading to v0.7.1 resolves the problem.

This version does not store lockAcquiredTimeUnixMs property when trustLocalTime configuration options is selected. Upgrading to v0.7.2 resolves the problem.

v0.6.3

Updated dependencies.

v0.6.2

It is now safe to not provide heartbeatTimeoutMs when constructing a FailOpen lock. Previously, omitting heartbeatTimeoutMs when creating a FailOpen lock would result in executing FailClosed lock release protocol on lock.release() invocation.

v0.6.1

Client no longer fails when attempting to validate configuration.

v0.6.0

aws-sdk is now a peerDependency instead of a devDependency per discussion in #19.

Reported problems:

This version fails when validating configuration, rendering the module unsuable. Upgrading to v0.6.1 resolves the problem.

Contributing factor to the failure was the use of outdated @hapi/joi calling convention.

v0.5.3

Upgraded @hapi/joi dependency to v16 which should be browser compatible.

Reported problems:

This version fails when validating configuration, rendering the module unsuable. Upgrading to v0.6.1 resolves the problem.

Contributing factor to the failure was the use of outdated @hapi/joi calling convention.

v0.5.2

Corrected invalid require("joi") to require("@hapi/joi") throughout.