Skip to content

An in-range update of request-promise is breaking the build 🚨 #5

@greenkeeper

Description

@greenkeeper

Version 4.2.1 of request-promise just got published.

Branch Build failing 🚨
Dependency request-promise
Current Version 4.2.0
Type devDependency

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

As request-promise is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • bitHound - Dependencies No failing dependencies. Details,- ❌ bitHound - Code 2 failing files. Details

Commits

The new version differs by 5 commits0.

  • ba7a320 Version 4.2.1
  • d65ff13 docs: example of cookie handling
  • 9ad707c fix: although this break backwards-compatibility with old request versions bumped up because of security vulnerability
  • cc30568 fix: depending on tough-cookie for npm < v3
  • fdc522a fix: using tough-cookie for the request

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions