An in-range update of request is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 2.79.0 of request just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | request |
| Current Version | 2.78.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As request is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 19 commits .
-
ff729c6Update changelog -
3a988202.79.0 -
ab94c86Merge pull request #2368 from forivall/patch-1 -
95b12d0Merge pull request #2394 from SimenB/files -
d05c86cUsefilesin package.json -
9f702bfMerge pull request #2463 from lostcolony/master -
7532634Remove redundant code -
d16bf18Merge branch 'master' into aws4-session -
67c9673Merge pull request #2467 from simov/bump-uuid -
39350edBump uuid -
e1c0981Merge branch 'defunctzombie-uuid' of github.com:antialias/request into bump-uuid -
9122f43Fixing requests/requests issue #2462 - AWS support does not include the use of session tokens for temporary credentials -
0131e2dMerge pull request #2459 from request/greenkeeper-taper-0.5.0 -
8c6fd17Merge pull request #2448 from mscdex/improve-new-test-reliability -
17095d5chore(package): update taper to version 0.5.0
There are 19 commits in total. 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 🌴
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failed AppVeyor build for the greenkeeper/request-2.79.0 branch and compare it with the passing CircleCI run. Inspect the project's request dependency and the 2.79.0 update; done means identifying the incompatibility or required adjustment and restoring a passing build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100