search

Kronos-Integration / test-step

kronos-step testing support with ava
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency rollup was updated from 1.0.1 to 1.0.2.

🚨 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](https://travis-ci.org/Kronos-Integration/test-step/builds/475711707?utm_source=github_status&utm_medium=notification)).
Release Notes for v1.0.2

2019-01-05

Bug Fixes

  • Make sure the transform hook is always reevaluated when a file watched by the hook changes (#2633)
  • Fix a crash when generating hashes for tree-shaken dynamic imports (#2638)
  • Fix a crash and some inconsistencies when using the acorn-bigint plugin (#2640)

Pull Requests

Commits

The new version differs by 7 commits.

  • 27cde2a 1.0.2
  • 6b55518 Update changelog
  • 6ac23e9 Make sure all CLI options are listed in the summary (#2641)
  • be7afed Treat bigints as unknown for now on all systems to avoid accidentally (#2640)
  • ee6db13 Do not fail when generating hashes for tree-shaken dynamic imports (#2638)
  • 29b8c64 Make code optional again in rollup warnings (#2635)
  • 6b343ab Make sure this.addWatchFile also declares transform dependencies, (#2633)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

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