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 rollup is breaking the build 🚨 #632

Closed
greenkeeper bot opened this issue May 28, 2020 · 2 comments
Closed

An in-range update of rollup is breaking the build 🚨 #632

greenkeeper bot opened this issue May 28, 2020 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 28, 2020


🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io


The devDependency rollup was updated from 2.11.0 to 2.11.1.

🚨 View failing branch.

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

rollup 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 failed (Details).

Commits

The new version differs by 3 commits.

  • 085cfc9 2.11.1
  • 2591660 Update changelog
  • 41778fe Handle side-effects next to side-effect-free default exports in case the default export is reexported (#3602)

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 28, 2020

  • The devDependency rollup was updated from 2.11.1 to 2.11.2.

Your tests are still failing with this version. Compare changes

Release Notes for v2.11.2

2020-05-28

Bug Fixes

  • Include side-effects in the second argument of Array.from (#3604)

Pull Requests

  • #3604: Mark Array.from as side-effectful, use two-argument Array.from when mapping Sets (@lukastaegert)
Commits

The new version differs by 3 commits.

  • 2040f82 2.11.2
  • 2b7d5d0 Update changelog
  • 21b015e Make Array.from as side-effectful, use two-argument Array.from when mapping Sets (#3604)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 28, 2020

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

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

1 participant