search

Kronos-Integration / kronos-service-registry

dummy service registry implementation
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

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

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency rollup was updated from 1.16.3 to 1.16.4.

🚨 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/kronos-service-registry/builds/553153819?utm_source=github_status&utm_medium=notification)).
Release Notes for v1.16.4

2019-07-02

Bug Fixes

  • Do not show a TypeScript error when providing a location as number to this.warn and this.error (#2974)
  • Use the correct TypeScript type for Sourcemap.version (#2976)

Pull Requests

Commits

The new version differs by 10 commits.

  • 2896755 1.16.4
  • c2eb6e6 Update changelog
  • b02296a Use async readFile in getRollupDefaultPlugin (#2965)
  • 20b434d Update changelog
  • eb97a3d Fix sourcemap type and update dependencies (#2976)
  • 959df58 Update changelog
  • 5682ae9 Align TS types, docs and implementation for this.warn and this.error (#2975)
  • 21b7ce4 Compensate for netlify URL normalization and fix scrolling again
  • 928d7d6 Update website links
  • 0dd6c15 Remove accidental solo test run

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.16.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.