An in-range update of whatwg-fetch is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Version 2.0.2 of whatwg-fetch just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | whatwg-fetch |
| Current Version | 2.0.1 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As whatwg-fetch 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
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
fetch 2.0.2Treat any non-Request arg to
new Request()as string urlSupport Tolerance Provision when parsing HTTP headers
Commits
The new version differs by 8 commits .
b337f95fetch 2.0.2c64c8a0Merge pull request #465 from github/url-to-stringb285e61Detect broken URL support in PhantomJS and skip testc1df102Treat any non-Request arg tonew Request()as string url9240ef4Remove secretsd7989c1Merge pull request #449 from woudini/tolerance-provisioneac7a2bSupport Tolerance Provision when parsing headersccea05dAdd test for cloning GET request
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
Inspect the project's whatwg-fetch dependency and start by reproducing the failure reported by the Travis CI build. Compare the 2.0.1 and 2.0.2 release notes and commits, then confirm the dependency change or compatibility fix by getting the build to pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100