Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

An in-range update of p-retry is breaking the build 🚨 #19

Closed
greenkeeper bot opened this issue Mar 31, 2019 · 1 comment
Closed

An in-range update of p-retry is breaking the build 🚨 #19

greenkeeper bot opened this issue Mar 31, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 31, 2019

The devDependency p-retry was updated from 4.0.0 to 4.1.0.

🚨 View failing branch.

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

p-retry 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

Release Notes for v4.1.0
  • Refactor TypeScript definition to CommonJS compatible export (#23) 71e51ad

v4.0.0...v4.1.0

Commits

The new version differs by 2 commits.

  • 9e2c016 4.1.0
  • 71e51ad Refactor TypeScript definition to CommonJS compatible export (#23)

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 Mar 31, 2019

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

@pvdlg pvdlg closed this as completed Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant