An in-range update of @hig/notifications-toast is breaking the build 🚨

## The dependency [@hig/notifications-toast](https://github.com/Autodesk/hig) was updated from `1.0.0` to `1.0.1`.

🚨 [View failing branch](https://github.com/Autodesk/hig/compare/development...Autodesk:greenkeeper%2Fdefault%2F%40hig%2Fnotifications-toast-1.0.1).

This version is **covered** by your **current version range** and after updating it in your project **the build failed**.

@hig/notifications-toast is a direct dependency of this project, and **it is very likely causing it to break**. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ✅ **ci/circleci: lockfile-update:** Your tests passed on CircleCI! ([Details](https://circleci.com/gh/Autodesk/hig/19341?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).
- ❌ **ci/circleci: bootstrap:** Your tests failed on CircleCI ([Details](https://circleci.com/gh/Autodesk/hig/19353?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)).

---

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start with the linked development-to-greenkeeper comparison and the failed CircleCI bootstrap run; the lockfile-update status passed while bootstrap failed after @hig/notifications-toast moved from 1.0.0 to 1.0.1. Trace the reported build failure and confirm the project builds and tests successfully with the dependency update.

Written by the indexing model from the issue text.