v0.6.2

Locksmith now internally handles DBus signals in a safer way, with additional checks on unexpected/malformed ones. This avoids a panic in the daemon component, which was frequently occurring on shutdown.

v0.6.1

locksmithd.service now runs After update-engine.service to prevent a race condition where it starts before update_engine and fails to initialize (#132)

v0.6.0

Locksmith no longer supports the deprecated best-effort strategy. The default
strategy is now reboot.

v0.5.0

Locksmith now writes an informational metadata file at the well known path
/run/update-engine/coordinator.conf.

Other tools that fulfill a similar role may also safely write to that file by
ensuring an exclusive lock is held on it for the duration of them running.

v0.4.2

Locksmith now uses Restart=on-failure in the systemd unit, so that if the reboot strategy is off, it is not constantly restart. Fixes coreos/bugs#1171.

v0.4.1

Locksmith no longer requires update-engine.service and does not have an ordering dependency on user-config.target and system-config.target due to the dependency loop when using coreos-cloudinit.

v0.4.0

Locksmith now uses github.com/coreos/etcd/client, instead of the deprecated
github.com/coreos/go-etcd.

Locksmith now uses github.com/coreos/pkg/capnslog for logging.

The reboot strategy best-effort is deprecated, and locksmithd will complain
loudly if it is used. Please use an explicit reboot or etcd-lock strategy
instead.

Locksmith logs some information about the configured reboot window.

Locksmith supports etcd basic auth.

Locksmith again requires update-engine.service, and will start after
user-config.target system-config.target are reached.

v0.3.4

The environment variables controlling reboot windows (REBOOT_WINDOW_START,
REBOOT_WINDOW_LENGTH) have been renamed to include the prefix LOCKSMITHD_
to maintain consistency with other locksmithd environment variables.

The old environment variables are still read to maintain compatibility with
locksmithd v0.3.1 to v0.3.3.

v0.3.3

Remove dependency on update-engine.service from locksmithd.service. If update-engine failed to start, systemd wouldn't start locksmith and the restart logic only applies if the service can be started.

v0.3.1

This release includes a number of new features and bug fixes - see the new CHANGELOG for full details.