An in-range update of object-assign is breaking the build 🚨

[greenkeeper]

Version 4.1.1 of object-assign just got published.

Branch	Build failing 🚨
Dependency	object-assign
Current Version	4.1.0
Type	dependency

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

As object-assign is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

• ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 9 commits .

• a89774b 4.1.1
• 2915ed4 Add inline MIT license with @license marker (#45)
• ba4ebc4 pin XO
• 6627d98 Add note encouraging built-in use (#41)
• f64a833 Store a reference to Object.getOwnPropertySymbols (#39)
• 022fe39 Add built-in Object.assign benchmarks (#40)
• ea6846a meta tweaks
• 066439e add missing test for target being a primitive (#34)
• 5174655 fix XO lint issues

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 4.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.