Change Details

Downstream dependencies have issues surfaced by `yarn audit` Checked the release notes: https://github.com/node-schedule/node-schedule/releases and there don't seem to be any breaking changes that affect us: It looks like the two breaking changes since are 1. Drop support for Node < 6 which doesn't affect us 2. "This removes support for passing job objects with an execute() method instead of a function... This is technically a breaking change, although this "feature" was never documented." which doesn't affect us either. checked `cron.js` which is the only place we use `node-schedule` and we aren't using the `execute()` approach anywhere

Downstream dependencies have issues surfaced by `yarn audit` Checked the release notes: https://github.com/node-schedule/node-schedule/releases and there don't seem to be any breaking changes that affect us: It looks like the two breaking changes since are 1. Drop support for Node < 6 which doesn't affect us 2. "This removes support for passing job objects with an execute() method instead of a function... This is technically a breaking change, although this "feature" was never documented." which doesn't affect us either. checked `cron.js` which is the only place we use `node-schedule` and we aren't using the `execute()` approach anywhere --- Depends on D3857

Downstream dependencies have issues surfaced by `yarn audit` Checked the release notes: https://github.com/node-schedule/node-schedule/releases and there don't seem to be any breaking changes that affect us: It looks like the two breaking changes since are 1. Drop support for Node < 6 which doesn't affect us 2. "This removes support for passing job objects with an execute() method instead of a function... This is technically a breaking change, although this "feature" was never documented." which doesn't affect us either. checked `cron.js` which is the only place we use `node-schedule` and we aren't using the `execute()` approach anywhere --- Depends on D3857