Update schema-utils to the latest version 🚀

[greenkeeper]

Version 1.0.0 of schema-utils was just published.

Dependency	schema-utils
Current Version	0.4.7
Type	devDependency

The version 1.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of schema-utils.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

v1.0.0

2018-08-07

Features

• src: add support for custom error messages (#33) (1cbe4ef)

Commits

The new version differs by 2 commits.

• 6ca2322 chore(release): 1.0.0
• 1cbe4ef feat(src): add support for custom error messages (#33)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[jsf-clabot]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ ev1stensberg
❌ greenkeeper[bot]

[evenstensberg]

@EugeneHlushko any breaking changes here?

[evenstensberg]

lgtm 💯

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[michael-ciniawsky]

There shouldn't be any breaking changes on propose, I just released it as major because I needed to change some internal options to be able to add custom error messages and to be 💯 safe downstream (just in case). Please open an issue in case it breaks something curious to see why :)

[evenstensberg]

Oki thanks!

[evenstensberg]

lgtm, awaiting CI

[ematipico]

All good

[ematipico]

I think the CI got stuck... @ev1stensberg any idea how to unstuck snyk?

[evenstensberg]

A rebase maybe. I’ll take a look later