Latest npm release of Enzyme (3.11.0) is using outdated object.assign

[katelynsills]

Current behavior

The latest npm release of Enzyme (3.11.0) is using object.assign v4.1.0, which has a bug that was fixed in 4.1.1. The master branch has been updated to v4.1.2, but no new npm release has been made. Would it be possible to release a new version of enzyme from master with the updated dependencies?

Version

library	version
enzyme	3.11.0

[ljharb]

It's using ^4.1.0, which is a semver range - thus, it's only an end-user lockfile that would be artificially keeping it at an old version. You can rerun npm install --save-dev enzyme and your lockfile will be updated with the newer one.

[ljharb]

In smaller packages, cutting a release for solely updating deps isn't that big a deal, so i'd usually do it on request, but enzyme is a bit more involved, and the main package isn't ready to be published until a number of other bugs are fixed, so I'm going to close this.

Note that any new users of enzyme, or upgraders to the latest version, will get the latest object.assign; it's only folks that were already on latest enzyme before the object.assign bugfix that will run into the need for an extra step.