An in-range update of coveralls 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.11.16 of coveralls just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | coveralls |
| Current Version | 2.11.15 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As coveralls 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
Commits
The new version differs by 13 commits .
8dfcfd6version bump4bc93acMerge branch 'master' of github.com:nickmerwin/node-coveralls671accaremoved codeship badgef390392Merge pull request #152 from ndaidong/masterde968b0Merge pull request #147 from hyperlink/update-request-dep72a4046Merge pull request #154 from a0viedo/patch-187b27f7Merge pull request #142 from Hirse/feature/travis-pr3edbecbMerge pull request #155 from kasperlewau/masterd117e3dreenable dronedd230f6don't hardcode minor versioncc0882dUpdate outdate dependencies99edf1aFix node-uuid deprecation by updating request dependencyf94b647Get PR number from TRAVIS
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 by inspecting the greenkeeper/coveralls-2.11.16 branch and the linked CircleCI and AppVeyor failures, then compare the coveralls 2.11.15 and 2.11.16 dependency changes. Done means the project’s CI passes with a compatible coveralls version or the dependency is safely held back.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100