This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of object.assign.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hello lovely humans,
object.assign just published its new version 4.0.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of object.assign. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 95 commits .
b7f770dv4.0.37087754Avoid usingreducesonpm run test:shams:corejspasses innodev0.8.4288052[Tests] only run linter checks in one node version (the latest).c491568[Deps] updateobject-keys64967ca[Dev Deps] updatetape,jscs,eslintb9567a3Support core-js's Symbol sham.cc69361Ensure that properties removed or made non-enumerable during enumeration are not assigned.3f83219[Tests] Refactor to use my conventional structure that separates shimmed, implementation, and common tests.8909128Createnpm run test:shamsand better organize tests for symbol shams.08a52d3[Tests] Removenspin favor ofrequiresafe.6cf3f56Avoid looking up keys and values more than once.efd12f2v4.0.294b027eEnsure correct property enumeration order, particularly in v8.b33d727[Deps] updateobject-keys,define-properties2493110[Dev Deps] updatejscs,eslint,@ljharb/eslint-configThere are 95 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgradeThis change is