Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of core-js is breaking the build 🚨 #123

Open
greenkeeper bot opened this issue Dec 2, 2019 · 5 comments
Open

An in-range update of core-js is breaking the build 🚨 #123

greenkeeper bot opened this issue Dec 2, 2019 · 5 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 2, 2019

The devDependency core-js was updated from 3.4.6 to 3.4.7.

🚨 View failing branch.

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

core-js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 3.4.7 - 2019.12.03
  • Fixed an NPM publishing issue
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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 2, 2019

After pinning to 3.4.6 your tests are passing again. Downgrade this dependency 📌.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 8, 2019

  • The devDependency core-js was updated from 3.4.7 to 3.4.8.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.4.8 - 2019.12.09
  • Added one more workaround for broken in previous versions inspectSource helper, #719
  • Added Opera Mobile compat data
  • Updated Samsung Internet, iOS, old Node and Android compat data mapping
  • es.string.match-all marked as completely supported in FF73
  • Generate core-js-compat/modules since often we need just the list of core-js modules

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 12, 2019

  • The devDependency core-js was updated from 3.4.8 to 3.5.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.5.0 - 2019.12.12

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 18, 2019

  • The devDependency core-js was updated from 3.5.0 to 3.6.0.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.6.0 - 2019.12.19
  • Added support of sticky (y) RegExp flag, #372, #732, #492, thanks @cvle and @nicolo-ribaudo
  • Added RegExp#test delegation to RegExp#exec, #732, thanks @cvle
  • Fixed some cases of Object.create(null) in IE8-, #727, #728, thanks @aleen42
  • Allowed object of minimum environment versions as core-js-compat and core-js-builder targets argument
  • Allowed corresponding to Babel targets.esmodules, targets.browsers, targets.node options in core-js-compat and core-js-builder
  • Engines in compat data and results of targets parsing sorted alphabetically
  • Fixed features/instance/match-all entry compat data
  • Fixed Array.prototype[@@unscopables] descriptor (was writable)
  • Added Samsung Internet 11 compat data mapping

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 25, 2019

  • The devDependency core-js was updated from 3.6.0 to 3.6.1.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 3.6.1 - 2019.12.25
  • Fixed a bug related Symbol with multiple copies of core-js (for 3.4.2-3.6.0), #736
  • Refactored some tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants