This release is functionally the same as v1.0.1. The GitHub credentials for
pushing releases were revoked, and so the push of v1.0.1 failed. v1.0.2 was
created, with proper credentials, to remedy this.

This patch release builds cronner against a supported runtime version (Go
1.10.4). We're not using 1.11 yet due to outstanding issues to be fixed in
1.11.1.

Note: Due to expired credentials, the release for v1.0.1 didn't complete successfully. The code itself was fine, but the step to push the binaries up to GitHub failed. This will be fixed as a v1.0.2 release.

This is the v1.0.0 release of cronner, which has been in development since
January 2015. cronner has been considered stable for a long period of time, so
it's only natural we would cut a v1.0.0 release. The v1.0.0 release includes
the following changes:

• require cronner be built against go 1.9+ to use monotonic time source
• use the dep utility, over glide, for dependency management
• add a Makefile for common tasks

There are no functional changes to the cronner codebase in this release. This
updates the Go runtime that cronner is built against to be go1.8.3.

• Add support for additional tags to be emitted with events and metrics using
  the -t/--tag flag. Thanks to Anthony O'Brien (@asobrien) for the contribution!

• build cronner against Go 1.7.5

Add -H/--statsd-host flag to allow users to override the host where statsd
metrics will be emitted to. Thanks to @andrecloutier-pd for the contribution.

• switch time keeping to use a monotonic clock instead of a wallclock
• add support for injecting environment variables to allow subprocesses to
  retrieve information about the cronner invocation
  • cronner can automatically slurp these environment variables to emit with
    events and metrics using the -P/--use-parent flag

• update the copyright years to include 2017
• use a constant raw literal string for the version string generation

This release of cronner includes the following changes:

• alter the output of the -v/--version flag
• build cronner against go1.7.4
• alter the build/release scripts to include a sha256 file

This also resolves an issue opened on PagerDuty/cronner: PagerDuty/cronner#48